Provider
ZapierIncident detail
Delayed processing for webhook-based triggers
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 are currently investigating an issue causing delays in the processing of webhook-based triggers. As a result, some Zaps that rely on trigger events may run later than usual. This may affect trigger events across a range of apps.
No trigger data is being lost — affected events are delayed, not dropped, and will be processed once the system catches up. Our team is actively investigating and working to restore normal processing times.
If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
Thank you for your patience.
Monitoring
A fix has been implemented and we are monitoring the results. We increased processing capacity to clear the backlog of delayed webhook-based trigger events, and trigger processing has returned to normal.
No trigger data was lost during the incident — affected events were delayed rather than dropped, and the backlog has now cleared. Our team is continuing to monitor processing times closely to ensure they remain stable.
If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
Thank you for your patience.
Resolved
This incident has been resolved. Earlier today, webhook-based triggers experienced processing delays when an unusually high volume of traffic from a third-party integration overwhelmed our shared trigger-processing system. As a result, trigger events across a range of apps were processed more slowly than usual, with delays peaking at around five minutes.
We increased our processing capacity to clear the backlog, and the third-party integration also applied mitigations on their end to reduce the excess traffic. Trigger processing has returned to normal and our systems are fully operational.
No trigger data was lost during the incident — affected events were delayed rather than dropped, and all delayed events have now been processed.
If you have any questions, or are running into any other issues, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
Thanks again for your patience while we were working on resolving that.
Keep exploring
More from Zapier
Neighboring incidents on Zapier's timeline and the rest of their record on OutageDeck.
← Older incident
Facebook Lead Ads intermittently missing leads
Newer incident →
Degraded performance for Zapier Agents
- 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