Help for owners
Zapier says I hit my task limit and my Zaps stopped running
Short answer
When you reach your task limit without pay-per-task billing, Zapier holds new Zap runs until the billing cycle resets. Held runs can be replayed after the reset or after an upgrade. Check the held runs first, then decide whether to wait, upgrade or turn on pay-per-task billing.
Does this sound like your situation?
- Orders, leads or emails stopped moving between my apps.
- Zapier sent me an email at 80 percent and another at 100 percent.
- Zap history shows runs as held, not as errors.
- Staff are copying data by hand because the automation went quiet.
- I do not know if the held items will ever be processed.
Why does this happen?
The limit holds runs, it does not delete them
Without pay-per-task billing, Zapier holds new Zap runs until the billing cycle resets. You get emails at 80 percent and 100 percent of the limit, and held runs can be replayed after the reset, after an upgrade, or after switching on pay-per-task billing.
Confirmed by help.zapier.com
Pay-per-task has its own ceiling
With pay-per-task billing, Zapier charges for tasks beyond the plan limit. The emails come at 80 percent and 100 percent of the pay-per-task limit, which is three times the plan's limit, and at 100 percent other tasks are held until the cycle ends.
Confirmed by help.zapier.com
A plan change can hold runs too
When a trial ends or the plan changes, runs that the new plan does not support are held, and Zapier keeps storing trigger data meanwhile. Actions that use paid features on a plan without them are held as well.
Confirmed by help.zapier.com
Something started far more runs than normal
A loop, a replay of old runs or a trigger set too widely can use a month of tasks in a day. Then the limit is a symptom, not the real problem.
What can I do about it today?
- Open Zap history and filter for held runsNote how many there are and which Zaps they belong to. This tells you what the business missed.
- Tell the people who rely on the dataIf invoices, bookings or lead alerts are held, staff need to know to check manually until the runs are replayed.
- Decide how to release the held runsWait for the reset, upgrade, or switch on pay-per-task billing. Each has a cost, so make that choice yourself.
- Replay after you understand the causeReplay held runs only once you know why the limit was reached, or the same thing happens again.
- Do not delete Zaps or connectionsRemoving them to stop the usage can break the flow for good.
When should I bring someone in?
- The held runs include payments, orders or customer messages that cannot be late.
- The usage spike has no explanation.
- The same limit is hit every month.
How do I handle it?
- Establish what was held and what is missingI list the held runs per Zap and compare them with what actually reached your apps.
- Find the cause of the usageI read the run history for loops, double triggers and wide filters, and rank the Zaps by tasks.
- Release the backlog safelyHeld runs are replayed in a controlled order, and where a Zap could create duplicates I check for existing records first.
- Prevent the next stopUsage alerts, tighter triggers and earlier filters are set up, so the account does not run into the wall unseen.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Are the held runs lost?
Zapier says you can resume by replaying held runs after the reset, after upgrading, or after enabling pay-per-task billing.
Does a held run cost tasks?
The task counting page says steps that do not run are not counted. Tasks are counted when steps run successfully, including on a replay of an entire run.
Can I just wait for the reset?
Yes, if the delay does no harm. If customers are waiting, that is a business decision for you to make.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.