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

Make RateLimitError (429): how to stop a scenario hitting the app's limit

You see: RateLimitError ยท 429

What it means

The scenario sent more requests to an app than its API allows in that window, so the app answered 429 and Make raised a RateLimitError.

How to fix it

  1. Turn on incomplete executions in the scenario settings, so a failed run is stored and retried instead of lost. Often the retry alone clears it.
  2. For an instant trigger, set a rate limit on the scenario; for a scheduled one, run it less often.
  3. Handle fewer records per run (around 20), and use the app's bulk modules where it has them.
  4. If it still trips the limit, add a Sleep module before the module that calls the app.

If it keeps coming back

Two scenarios calling the same app share its limit. Spread their schedules apart, or merge 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