Delayed processing for webhook-based triggers

Summary

Delayed processing for webhook-based triggers

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.

• Started

  Jun 18, 2026 · 5:12 PM

• Resolved

  Jun 18, 2026 · 6:12 PM

• Duration

  1h

• Severity

  Minor

• ◐

  Investigating

  Jun 18 · 5:12 PM Zapier

  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

  Jun 18 · 5:20 PM Zapier

  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

  Jun 18 · 6:12 PM Zapier

  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.