Task MeterGuide

Zap runs on hold after the task limit: what's kept and how to replay

Updated 2026-10-11 · by Hieu Tran, written with AI agents and checked against the sources below

When your account reaches its plan's task limit and pay-per-task is off, Zapier holds new Zap runs instead of running them. Nothing runs until you add tasks or the cycle resets, and the held runs then wait for you: Autoreplay doesn't touch them.

Getting the held runs through

1. Fix the cause first: upgrade the plan, turn on pay-per-task, or wait for the cycle to reset. Replaying before that just holds them again.
2. Open Zap history, filter by status Held, select the runs and replay them. Each replayed step uses tasks like a normal run.
3. Replay them soon. Zapier guarantees at most 60 days of run data in Zap history (and shows up to 10,000 runs), and steps can only be replayed within 60 days of the trigger.
4. Mind the order: replayed runs process now, so a held "update" may land after a newer one.

Other reasons runs get held

• A disconnected app account: reconnect it, then replay.
• An expired payment method.
• Flood protection: one check for new data would start 100 or more runs.
• An app your Team or Enterprise admin has restricted, or a premium app your plan doesn't include.

So it doesn't happen next month

Forecast where you'll land before the cycle ends: tasks used so far ÷ days elapsed × days in the cycle. If that's over the limit, decide in advance between pay-per-task (2.5× the base rate on monthly plans, 1.25× on annual, capped at 3× your plan's tasks) and the next tier, rather than finding out from held runs.

More guides

• Hit your Zapier task limit? What it costs and how to cut tasks
• Why one Zap is eating your tasks, and how to stop it