We identified an issue where a very small fraction (less than 0.0012 percent) of Zap triggers did not retry after encountering an unexpected error.
This resulted in a very low but ongoing loss of automations.
Impact:
The issue had been present for some time and affected hundreds of triggers per day, compared with ~1 billion successful executions daily ( less than 0.0001 percent of traffic). While the overall impact was minimal, we understand even small disruptions can affect critical workflows.
Root Cause:
Zap triggers run on background tasks designed to retry after encountering an error. We discovered that, in rare cases, these tasks were stopping before the final retry could complete. Because of this, some Zaps that should have run were silently dropped instead.
Resolution:
A permanent fix has been deployed and verified; no customer action is required. We are also improving how Zap triggers are processed to further increase reliability and prevent similar issues in the future.
We’ll continue monitoring closely to ensure stability. If you notice anything unusual with your Zaps, our Support Team is here to help: https://zapier.com/app/get-help
Posted Sep 10, 2025 - 16:39 PDT
This incident affected: Zaps (Instant Triggers, Polling Triggers).