Provider
ZapierIncident detail
Delays between Zap execution
Timeline window
to
Get alerted the next time Zapier breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We have identified delays between Zap execution and when runs become visible in Zap History. Importantly, Zap executions themselves are not failing or delayed — this issue only impacts the visibility of Zap History data in the UI.
Our team is actively investigating the issue and we will continue to provide updates as soon as more information becomes available.
Resolved
This issue has been resolved. The delays between Zap execution and when runs become visible in Zap History are no longer occurring. Zap History data should now be appearing in the UI as expected.
As noted in our earlier update, Zap executions themselves were not impacted — this issue only affected the visibility of run data in the UI.
Thank you for your patience while our team worked on this. If you continue to experience any issues, please don't hesitate to contact support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
Keep exploring
More from Zapier
Neighboring incidents on Zapier's timeline and the rest of their record on OutageDeck.
← Older incident
Code Steps failing with "No response from child process" across Zaps/APIs
Newer incident →
Code by Zapier seeing errors
- zapier-dev-files.s3.amazonaws.com is tagged as "dangerous site" by GoogleMinor · Active
- Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.Major
- Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)Minor
- Agent runs (agents.zapier.com) intermittently experiencing 429 errorsMinor