Resolved
The issue has now been resolved and we have directly notified all customers who were impacted by this outage.
We’re sorry for any inconvenience caused.
Monitoring
Between 16:33 and 18:01 UTC on July 21, 2026, some workflows failed to trigger correctly.
What happened: An infrastructure configuration change deployed shortly before the incident caused an error when encrypting the content of newly received workflows, which caused some workflow triggers not run properly.
What we did: We reverted the change and corrected the underlying infrastructure configuration. All impacted workflow triggers resumed processing normally by 18:01 UTC, and we've since confirmed triggers are operating correctly.
We’re continuing to investigate recovering runs triggered during this timeframe. We’ll update this page as soon as we have an update.
Monitoring
Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.
Identified
An issue has been been identified.
We have identified the root cause and our team is working to resolve the issue as quickly as possible.
Investigating
We're investigating reports of workflows failing to trigger.
We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
