Zapier · Rate limits

Throttled by Zapier / Zapier has blocked this task

Short answer

These Zapier errors mean the Zap made too many requests to Zapier or a connected app within a short period and exceeded a rate limit. Replay the run, add a Delay After Queue step, or adjust the flood protection limit on a paid plan.

VerifiedLast verified

01Error text

Zapier error
Throttled by Zapier! Max ... runs per ... seconds.
Too much data received for one task (... bytes), Zapier has blocked this task.
Too much data received (... *... bytes) within a ... second window, Zapier has blocked this task. Resets in ... seconds.

02Likely causes

  • The Zap makes too many requests to Zapier or a connected app within a short period.
  • This exceeds a rate limit, imposed either by Zapier or by the app.

03How to fix it

  1. Review the rate limits article to determine whether the issue is related to Zapier or the app. Look for "Zapier" in the message.
  2. If the message mentions a second window or a maximum number of runs per second, replay the Zap run.
  3. Add a Delay After Queue step to the Zap, which holds actions for a set time before running them.
  4. On a paid Zapier plan, adjust the flood protection limit on the Zap.

iNotes

The run shows a stopped status in Zap history. The "..." parts are values Zapier fills in.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for Zapier work:Open Zapier jobsZapier rates and salaries

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.