Zapier: Zap turned off automatically due to errors
Last verified
Your Zap was turned offWhat it means
Zapier automatically turns off a Zap that keeps failing. According to Zapier's help center, a Zap is turned off when it errors 95% of the time it runs and has run more than 20 times in the past 7 days. Only runs with the Errored status count; Safely halted and Handled error runs do not.
Team and Enterprise accounts get a warning first: Zapier emails the account owner and gives a grace period before turning the Zap off, 24 hours on Team and 72 hours on Enterprise. On other plans, the first notice is often the email saying the Zap was turned off.
A Zap can also be turned off for reasons other than errors, for example losing access to a paid feature it uses (multi-step Zaps, premium apps) after a trial ends or a plan is downgraded. The Change History in the Zap editor shows when and why it changed state.
What is not wrong: turning the Zap back on will not help on its own; it will be switched off again if the errors continue.
What it looks like
Automatic turn-off rule (Zapier help center):
errors on 95% of runs AND more than 20 runs in the past 7 days
Team: 24-hour grace period Enterprise: 72-hour grace periodWhy it happens
- A connected account was disconnected or its token expired, so every run fails.
- A required field is now empty or invalid because the trigger data changed.
- The destination app changed its API or permissions.
- A trial ended or the plan was downgraded and the Zap uses a paid feature.
How to fix it
- Open Zap history, filter by Errored and read the most common error message.
- Fix that error first (reconnect the account under Apps, remap fields, update the step).
- Test the step in the editor until it succeeds.
- Check the Zap's Change History to confirm why it was turned off.
- Turn the Zap back on and replay failed runs if needed.
How to stop it recurring
Enable error notifications, add error handlers for steps that can fail for expected reasons, and use Filters or Paths to stop runs with incomplete data before they reach strict actions. A Zap that halts safely is never turned off for that reason; see Safely halted.
Official documentation: help.zapier.com/hc/en-us/articles/8496216132621-Zap-is-not-running. See all Zapier error messages or the Zapier limits and quotas.
Related errors
Definitions
Quick answers
What does "Zap turned off automatically due to errors" mean in Zapier?
Zapier automatically turns off a Zap that keeps failing. According to Zapier's help center, a Zap is turned off when it errors 95% of the time it runs and has run more than 20 times in the past 7 days. Only runs with the Errored status count; Safely halted and Handled error runs do not.
How do I fix "Zap turned off automatically due to errors"?
1. Open Zap history, filter by Errored and read the most common error message. 2. Fix that error first (reconnect the account under Apps, remap fields, update the step). 3. Test the step in the editor until it succeeds. 4. Check the Zap's Change History to confirm why it was turned off. 5. Turn the Zap back on and replay failed runs if needed.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.