Zapier · Replaying Zap runs
Zap has diverged too much
Short answer
This 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.
VerifiedLast verified
01Error text
Task was stopped because its Zap has diverged too much02Likely causes
- You make significant changes to a Zap after it has started a run, then try to replay an errored step. Significant changes are altering the order of steps, the number of steps, or the apps used.
- A delayed run is still pending from a previous version of the Zap.
03How to fix it
- Replay the entire Zap run.
iNotes
You cannot replay the errored steps individually, even if you revert the Zap to its previous version.
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.
- 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