Zapier Turned Off Your Zap Because of Errors: Find and Fix the Cause
Short answer: Zapier switches a Zap off when its runs keep failing, so a broken step does not keep producing errors forever. To recover, open Zap history, filter by the errored or halted status, and read the message on the first failed step: it is usually an expired app connection, a field that no longer exists, or a rate limit. Fix that cause, test the step, turn the Zap back on, then replay the failed runs so the missing leads or orders arrive. Finally, add a filter to block bad data and check your error notification settings so the next failure reaches someone quickly.
How you usually find out
The story is often the same. A landscaping company gets its web form leads into a CRM through Zapier. On Monday the sales lead notices nobody has called for three days. The Zap dashboard shows the Zap as off, with a note about errors. Somewhere inside the Zap history is a list of runs that did not finish, and each of those is a lead that never reached the CRM.
The good news: Zapier keeps those runs for a period, so in most cases you can reprocess them after the fix rather than retyping data.
Step 1: Read Zap history by status
Open Zap history from the left menu and filter by your Zap. Then filter by status:
| Status | Meaning | What to do |
|---|---|---|
| Errored | A step failed and the run stopped | Read the error, fix, replay |
| Halted | A step stopped the run on purpose or could not continue | Check whether it was a filter or a real problem |
| Filtered | A filter step ended the run as designed | Usually fine, confirm the rule is correct |
| Success | Run completed | Spot-check one to compare with failures |
Click into the oldest errored run. The first red step is where the problem starts. Read the full error text and look at the data that came in from the trigger. Compare it with a successful run from before the trouble started; the difference usually jumps out.
Step 2: Identify the common cause
Expired or disconnected app connection
Messages mentioning authentication, an invalid token or a permission issue mean the app account linked to Zapier lost access. It happens when someone changes a password, leaves the company, or when the app revokes old tokens.
Fix: go to the Apps or Connections area, reconnect the account, ideally using a shared business login rather than a personal one, then select the reconnected account in the Zap step.
A field or option changed
Someone renamed a form field, deleted a dropdown option in the CRM, or removed a custom field. The Zap still tries to map the old one, and the receiving app rejects the request. Errors often name a missing field, an invalid value, or a required field that came through empty.
Fix: open the step, refresh the fields, remap the changed field, and test with fresh sample data.
Rate limits and timeouts
If many triggers arrive at once (a newsletter launch, an imported spreadsheet), the receiving app may reject requests with a "too many requests" style error. Zapier retries some of these, but a burst can still produce errors.
Fix: add a Delay step or use Zapier's queueing options for that step, and avoid bulk imports that fire the trigger for every old row.
Bad incoming data
An email field with a space, a phone number in a weird format, an empty name. The action step refuses the record.
Fix: add a Formatter step to clean values, and a Filter (covered below) to stop records that cannot succeed.
Step 3: Turn it back on and replay
Once the cause is fixed and the step tests successfully:
- Turn the Zap on.
- Go back to Zap history, filter errored runs for that Zap, and select them.
- Use Replay on the selected runs. Zapier reruns them with the current version of the Zap, starting from the failed step.
- Watch the first two or three replays finish before replaying the rest.
- Open the target app (CRM, sheet, helpdesk) and confirm the records arrived with correct values.
Replay availability depends on your plan, and runs older than the history retention period cannot be replayed. Check Zapier's article on viewing and managing Zap history for the current rules. For anything outside that window, export the entries from the source app (for example form submissions between two dates) and import them manually.
Autoreplay
On plans that include it, autoreplay retries failed runs automatically after a delay. It is useful for short outages at the receiving app but will not fix a mapping or connection problem, so do not rely on it to cover real breakages.
Step 4: Add filters so bad data does not break the Zap
A Zap that errors on every junk submission will get switched off again. Put a Filter step right after the trigger that only continues when the record looks valid:
- Email contains "@"
- Name field exists
- Form name is the one you expect (if several forms share the trigger)
Records that fail the filter show as filtered rather than errored, which does not count toward the error shutdown. Add a second path, if needed, that sends filtered records to a "check manually" sheet so nothing disappears quietly.
Step 5: Set error notifications properly
Zapier emails the account owner about errors by default, which is useless if that inbox belongs to someone who left, or is a busy shared address. In your settings, review notification options for errors and pick an option that alerts immediately rather than in a summary. Then:
- Make sure the address receiving alerts is read daily by someone responsible.
- Consider a Zap-level error handler or a separate Zap that posts to a team chat channel when something fails, if your plan supports it.
- Add a weekly calendar reminder to glance at Zap history for each critical Zap.
Prevent the next shutdown
- Use a shared admin login for app connections, not an individual's account.
- Tell whoever edits forms and CRM fields that a Zap depends on them.
- Name Zaps clearly ("Website quote form to CRM, new lead") so alerts are understood.
- Keep one test submission per month as a smoke test.
FAQ
Why did Zapier turn off our Zap without warning?
It probably did warn, by email to the account owner. Check that address and its spam folder, then update notification settings.
Will replaying create duplicate records?
Only for runs that partially succeeded before failing. Check whether earlier steps (like creating a contact) completed, and add a "find or create" step to avoid duplicates.
Can we replay runs from last month?
Only if they are still within your plan's history retention. If not, export the data from the source and import it.
Is there a limit on how many errors trigger the shutdown?
Zapier uses an error threshold that it documents in its help center. The exact behavior can change, so check its current article rather than relying on a number.
If your lead or order automations break more often than they should and you want them rebuilt on a sturdier footing, drop us a note and we will take a look.