Playbooks unable to run

Update timeline

1. investigating Jul 27, 2026, 07:50 AM UTC

   An unexpected cloud provider maintenance is currently affecting our Playbooks automations services. Our engineering team is currently investigating the issue and trying to restore services in a timely manner. We thank you for your patience during resolution.

2. investigating Jul 27, 2026, 09:22 AM UTC

   We are experiencing an outage caused by an unexpected infrastructure restart. We are pushing our Cloud Provider for immediate resolution to bypass the provider's standard recovery timeframe. We will keep you informed

3. identified Jul 27, 2026, 10:39 AM UTC

   We are still pending the restart completion for impacted component infrastructure which is currently impacting our Playbooks functionality. Our engineering team is in permanent contact with cloud provider teams to ensure the restart is performed in a timely manner. We thank you for your patience during resolution.

4. identified Jul 27, 2026, 02:36 PM UTC

   We are continuing to work on a fix for this issue.

5. identified Jul 27, 2026, 02:39 PM UTC

   Despite cloud provider rollover, the affected resources are still unavailable, and the Playbooks functionality are still heavily impacted. Our engineering teams are still in direct contact with Cloud provider to recover the situation as soon as possible. We thank you for your patience during the resolution of this incident.

6. identified Jul 27, 2026, 06:13 PM UTC

   Following an underlying cloud provider issue, we are required to rebuild part of our Playbook infrastructure. Our engineering team is fully focused on re-deploying the environment as quickly and safely as possible.

7. monitoring Jul 28, 2026, 06:13 AM UTC

   Our Engineering team has been fully mobilized overnight to rebuild our Playbook infrastructure. Playbooks are now fully available. Our team is now focused on replaying actions and triggers impacted by the incident. We thank you again for your demonstrated patience during the resolution of this incident

8. monitoring Jul 28, 2026, 10:36 AM UTC

   Actions and triggers impacted by the incident are being replayed. Our engineering team is monitoring closely the situation, and current estimation provides a completion ETA by 1.30 pm CET for the replay to complete. During the incident, some users faced issues with triggers unable to start and remaining in inconsistent state. Those triggers have been stopped, and can now be restarted manually by users. A final update will be provided when replay operations are complete.

9. resolved Jul 28, 2026, 05:09 PM UTC

   The incident has been resolved, we are back to real-time processing, and everything is stable.