Turned off or holding: tell them apart first
Zapier documents two different things that both look like a Zap that stopped working. A Zap can be turned off, which happens when it errors too often. Or the Zap stays on but its runs are held, which happens when your account hits a limit or loses access to something the Zap needs. Zapier's "Zap is not running" article covers both. [1]
Check Zap history first. Its statuses tell you which case you are in, and Zapier's troubleshooting guide starts there: find the error in Zap history or the Zap editor, use the step's Troubleshoot or Logs tab to see the HTTP status code, fix the cause, then recover the runs. [3]
| What you see | Documented cause | Is it a plan limit? | Fix |
|---|---|---|---|
| Zap switched off | Errors 95% of the time and ran more than 20 times in 7 days [1] | No | Fix the failing step, turn on, replay [1] [4] |
| Runs held, "Task limit reached" | Plan's tasks used up, or a premium app not on your plan [2] | Yes | Upgrade or wait for the cycle to reset, then replay [1] |
| Runs held, premium feature | Multi-step, Paths or premium apps on an unsupported plan [1] | Yes | Upgrade or remove the feature, then replay [1] |
| Runs held, "Trial ended or plan changed" | New plan lacks a feature the Zap uses [2] | Yes | Upgrade, replay; contact Support if you did not change plans [2] |
| Runs held, "Disconnected app" | An app account is no longer connected [2] | No | Reconnect, then replay [2] [5] |
| Runs held, "Payment issue" | Payment details lapsed [2] | No | Update payment method, replay [2] |
| Runs held, "Too much data" | A trigger check found 100 or more new items [2] | No | Add a Delay After Queue step [2] |
| Runs held, "Step limit reached" | Zap has more than 100 steps [2] | No | Split into two or more Zaps [2] |
Cause 1: the Zap errored too many times
Zapier's help says it turns off a Zap that "Errors 95% of the time it runs" and "Has run more than 20 times in the past 7 days." Team and Enterprise accounts get an email to the account owner and a grace period before shutdown: 24 hours on Team and 72 hours on Enterprise. [1]
To fix it, open Zap history, find the step that fails, and match its HTTP status code to the cause Zapier lists: 401 for an expired or revoked access token or a changed app password, 403 for insufficient permission, 404 for a record that does not exist, 422 for data in the wrong format or missing required data, and 429 for exceeding Zapier's or an app's rate limit. [3] Correct the step, publish, turn the Zap back on, and replay the errored runs. [4]
If some errors are expected, paid plans can set "Keep running if errors occur" under Error ratio override in the Zap's advanced settings. It needs edit access, is not available on the Free plan, and Zaps with it enabled skip the grace period. [1] Custom error handling, which runs an alternative path when a step fails, is the more durable fix. [3]
Cause 2: task limits, plan changes and payment
When an account reaches its task limit for the billing cycle, Zapier holds all actions in all Zaps. On plans without pay-per-task billing, new runs stay held until the cycle resets, you upgrade or you turn on pay-per-task billing. On plans with pay-per-task billing, Zapier emails at 80% and at 100% of the pay-per-task limit, which is three times the plan's task limit, and holds tasks after that. [1] [6]
A task is a successful action; triggers, filters, paths, tests and failed steps do not count. [6] The Free plan includes 100 tasks a month and only two-step Zaps, with no premium apps; Professional starts at $19.99 a month billed annually, or $29.99 monthly, for 750 tasks. [7] A downgrade from a Team plan, an ended trial or a lapsed payment also holds runs that the account can no longer support. [2]
This is the case where paying more actually fixes the Zap. If the history shows "Task limit reached" or a plan-related hold, nothing in the Zap is broken; either raise the limit or wait for the reset, then replay. [1]
Cause 3: a disconnected or expired app
Held runs marked "Disconnected app" mean an app account in the Zap is no longer connected. [2] On the App Connections page, an expired connection shows a Reconnect button, available only for connections you own. Reconnecting restores the account "for all Zap workflows, agents, and other Zapier products that use it." [5]
Deleting a connection is different: Zapier loses access to that account, and you must replace the connection in every Zap that used it or those Zaps may stop running. When a shared connection is revoked, published Zaps that rely on it pause. [5]
Restart and replay, step by step
- Read the status and reason in Zap history before changing anything. [3]
- Fix the cause: the failing step, the connection, the payment method or the plan. [1] [2]
- If you edited the Zap, publish it before replaying so the edited version runs. [4]
- Turn the Zap on; Zapier says a Zap must be on before you can replay an entire run. [4]
- Select held or errored runs in Zap history and replay them, up to 5,000 at a time. [4]
- Remember that replaying an entire run counts tasks again, even for steps that succeeded before. [4]
- On paid plans, turn on Autoreplay for temporary errors; it is not on the Free plan. [4]
- If you changed the trigger app or event, replay is no longer possible; rebuild missed records another way. [4]
What the Free plan can and cannot recover
Free accounts can manually replay errored runs, but not held runs, and they cannot use Autoreplay or replay an entire Zap run. Those need Professional, Team or Enterprise. [4] Zapier says it keeps storing trigger data while runs are held, so nothing is lost while you decide whether to upgrade. [2]
If your Zap regularly hits the 100-task Free limit, count tasks per run before choosing a tier: a two-step Zap uses one task per successful run, so 100 tasks covers about 100 triggering events a month. [6] [7]
Questions before you decide
Why did Zapier turn my Zap off?
Zapier's help says it turns off a Zap that errors 95% of the time it runs and has run more than 20 times in the past 7 days. Check Zap history for the failing step and fix it before turning the Zap back on.
Will I lose the data from runs that were held?
Zapier says it keeps storing trigger data while a run is held and that no data is lost once you fix the cause and replay the run.
Can I stop Zapier turning off a Zap with errors?
On paid plans, the Zap editor's advanced settings have an Error ratio override called Keep running if errors occur. It is not available on the Free plan, and Zaps using it skip the grace period.
Can I replay runs on the Free plan?
Free plans can manually replay errored runs only. Replaying held runs, Autoreplay and replaying an entire Zap run require Professional, Team or Enterprise.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Zapier Help: Zap is not running Accessed 30 Oct 2026
- Zapier Help: How to troubleshoot held Zap or step runs Accessed 30 Oct 2026
- Zapier Help: Troubleshoot Zap workflows Accessed 30 Oct 2026
- Zapier Help: Replay Zap runs Accessed 30 Oct 2026
- Zapier Help: Manage your app connections Accessed 30 Oct 2026
- Zapier Help: How is task usage measured in Zapier Accessed 30 Oct 2026
- Zapier pricing Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.