← Void · A-to-Mind · Fix an automation

"Throttled by Zapier" or 429 Too Many Requests: how to slow a Zap down

You see: Throttled by Zapier · Zapier has blocked this task · 429 Too Many Requests

What it means

The Zap made too many requests in a short time, to Zapier or to the app it calls, so the requests were held back. Big imports, loops and bursts of new records are the usual cause.

How to fix it

  1. Replay the throttled or blocked runs from Zap history once the burst has passed.
  2. Add a Delay step (or Delay After Queue) before the step that calls the app, so runs go out one at a time instead of all at once.
  3. If the Zap loops over many items, process fewer per run.
  4. If it keeps happening with normal traffic, check Zapier's status page and the app's status page for an outage.

If it keeps coming back

A 429 from the app itself means its own rate limit: check that app's API limits for your plan, and space the Zap's calls to fit under them.

Still stuck? Ask Void, free

Paste the error and what the automation does. Void names the likely cause and the fix, in seconds, no account.

Ask Void about this error

Or have it fixed: $25

One broken automation, diagnosed and repaired, with proof it runs again. Reply to the receipt with what stopped.

Get the One-Time Fix

The One-Time Fix covers one workflow. What you send and what you get back.

Sources