The incident affecting some custom action steps has been resolved.
Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions.
Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.
No components marked as affected
Resolved
The incident affecting some custom action steps has been resolved.
Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions.
Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.
Monitoring
Impact: Some customers may have seen failed or delayed workflow runs for a short period while we addressed a service issue.
What happened: A brief spike in internal traffic put strain on systems that support authentication and request handling for certain workflow actions. That led to errors or slowdowns for workflows using those paths.
Current status: The issue is resolved. Contributing factors have been addressed, capacity has been adjusted, and services are operating normally. We’ve worked through recovery steps for affected work, with checks showing things completing as expected.
What you may have experienced: If your Zaps use custom actions, you might have seen failures or delays during the incident window. Affected work has been replayed or recovered where applicable.
