Zapier Status · History · Incident #7038
RESOLVEDWebhook Triggers and Zap Actions - Service Disruption
Minor · Started Sep 8, 2026 · 2:06 PM
Zapier Status · History · Incident #7038
RESOLVEDMinor · Started Sep 8, 2026 · 2:06 PM
Duration
3h 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved. If you're still seeing issues with a Zap that should have run during this window, contact Support: [zapier.com/app/get-help](http://zapier.com/app/get-help "zapier.com/app/get-help")
Started
Sep 8, 2026 · 2:06 PM
Resolved
Sep 8, 2026 · 5:08 PM
Duration
3h 1m
Severity
Minor
Event timeline
Monitoring
Sep 8 · 2:06 PM ZapierA brief infrastructure issue between approximately 8:15–9:50 AM ET caused some Zap workflows using webhook triggers to not fire, and some Zap action steps to fail. The issue has been resolved, and Zap Runs are processing normally. We're reviewing affected accounts and replaying missed webhook events where possible. If you notice a Zap that should have run during this window and did not, contact Support: [zapier.com/app/get-help](http://zapier.com/app/get-help "zapier.com/app/get-help")
Resolved
Sep 8 · 5:08 PM ZapierThe issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved. If you're still seeing issues with a Zap that should have run during this window, contact Support: [zapier.com/app/get-help](http://zapier.com/app/get-help "zapier.com/app/get-help")
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.