Zapier · Zap history
Task was stopped because its Zap was turned off
Short answer
This 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.
VerifiedLast verified
01Error text
Task was stopped because its Zap was turned off02Likely causes
- You turned the Zap off while it was running.
- The Zap errored too many times and was turned off while running.
- There could be an issue or outage with your app or Zapier.
03How to fix it
- Review any errors for this Zap in Zap history, then fix those errors.
- Turn the Zap back on.
- Check for an outage in the app or on the Zapier Status page.
- Replay any failed Zap runs.
04Official documentation
→Related errors
- 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.
- Zap errored too many times and turned offZapier 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.
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