Zapier: Throttled by Zapier / Zapier has blocked this task
Last verified
Throttled by Zapier! Max ... runs per ... seconds.What it means
Zapier uses these messages when a Zap exceeds a rate or data-volume limit. The help center lists three forms: "Throttled by Zapier! Max ... runs per ... seconds.", "Too much data received for one task (... bytes), Zapier has blocked this task.", and "Too much data received (... bytes) within a ... second window, Zapier has blocked this task. Resets in ... seconds."
The first means too many runs in a short window. The other two mean a single task, or a burst of tasks, carried more data than Zapier allows. Affected runs often pile up with a stopped status. Related protections include flood protection, which holds runs when 100 or more events trigger a polling Zap at once, and per-app limits set by the connected app.
What is not wrong: your Zap's logic. The volume is the problem.
What it looks like
Too much data received (... bytes) within a ... second window, Zapier has blocked this task. Resets in ... seconds.Why it happens
- A bulk import or backfill triggers many runs at once.
- A loop or webhook source sends events faster than the limit.
- A single trigger event carries a very large payload, such as a big file or array.
- Several Zaps share the same app limits.
How to fix it
- Read which variant you have: runs per seconds (rate) or bytes (data volume).
- For rate or time-window messages, replay the affected runs after the window resets.
- Add Delay After Queue so runs execute one after another instead of all at once.
- On paid plans, adjust the Zap's flood protection limit if the bursts are expected.
- For data-size blocks, send a link or ID instead of the whole payload and fetch details in a later step.
How to stop it recurring
Batch bulk operations outside Zapier or spread them over time, keep webhook payloads small, and use queues or delays for bursty sources. See Zapier's Zap limits article for current numbers.
Official documentation: help.zapier.com/hc/en-us/articles/8496038845325. See all Zapier error messages or the Zapier limits and quotas.
Related errors
Definitions
Quick answers
What does "Throttled by Zapier / Zapier has blocked this task" mean in Zapier?
Zapier uses these messages when a Zap exceeds a rate or data-volume limit. The help center lists three forms: "Throttled by Zapier! Max ... runs per ... seconds.", "Too much data received for one task (... bytes), Zapier has blocked this task.", and "Too much data received (... bytes) within a ... second window, Zapier has blocked this task. Resets in ... seconds." The first means too many runs in a short window.
How do I fix "Throttled by Zapier / Zapier has blocked this task"?
1. Read which variant you have: runs per seconds (rate) or bytes (data volume). 2. For rate or time-window messages, replay the affected runs after the window resets. 3. Add Delay After Queue so runs execute one after another instead of all at once. 4. On paid plans, adjust the Zap's flood protection limit if the bursts are expected. 5. For data-size blocks, send a link or ID instead of the whole payload and fetch details in a later step.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.