Zapier · Zap on/off state
Zap errored too many times and turned off
Zapier turns a Zap off automatically when it errors 95% of the time it runs and has run more than 20 times in the past 7 days. Troubleshoot the errors in the Zap, or enable error ratio override so it keeps running.
VerifiedLast verified
01Error text
Your Zap errored too many times02Likely causes
- The Zap errors 95% of the time it runs, and has run more than 20 times in the past 7 days.
03How to fix it
- Troubleshoot the errors in the Zap.
- Optionally enable error ratio override and choose "Keep running if errors occur".
- Turn the Zap back on.
iNotes
Team plan accounts get a 24-hour grace period and Enterprise accounts a 72-hour grace period before the Zap turns off. Error ratio override is available on Professional, Team and Enterprise plans.
04Official documentation
→Related errors
- Task was stopped because its Zap was turned offThis Zapier error appears in a Zap run when the Zap was turned off while it was running. Fix any errors for the Zap in Zap history, turn the Zap back on, then replay the failed runs.
- Zap has diverged too muchThis Zapier error appears when you replay an errored step after making significant changes to the Zap since the run started. Replay the entire Zap run instead of the individual step.
- On hold (held Zap run)An On hold Zap run is waiting for an issue to be fixed before it can continue. Fix the cause, such as a disconnected app, a reached task limit or a payment issue, then replay the held run.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Zapier work:Open Zapier jobsZapier rates and salaries