Playbook execution disruption

Incident Report for SEKOIA FRA1

Resolved

The playbook service is fully operational and this incident is now closed. The execution lag has been fully caught up, and all pending playbooks have been processed.
Posted Oct 29, 2026 - 16:57 UTC

Monitoring

We have applied fixes to our infrastructure to absorb the remaining load of pending playbooks, and executions are now running normally. All pending playbooks should now have been processed. Our team continues to monitor the situation closely.
Posted Oct 29, 2026 - 16:10 UTC

Identified

Playbook executions have resumed and the backlog is being processed progressively. Our team is working to speed up the processing of pending executions and to put measures in place to prevent this issue from happening again. We will share another update as soon as possible.
Posted Oct 29, 2026 - 15:09 UTC

Update

We are still investigating the root cause of the issue. In parallel, our team is carrying out operations on our infrastructure to resolve the problem. New playbooks still cannot be started at this time. We will share another update as soon as possible.
Posted Oct 29, 2026 - 14:37 UTC

Investigating

We are currently experiencing an issue with our playbook execution engine. New playbooks cannot be started at this time. Our team is actively investigating and working on a fix. We will provide an update as soon as we have more information.
Posted Oct 29, 2026 - 14:05 UTC
This incident affected: Automation.