Try or ByeTry or Bye

Make RateLimitError (429 Too Many Requests)

Workaround available Web Updated October 21, 2026

Quick answer

RateLimitError is the HTTP 429 response from the connected app (or from Make's own webhook limit of 300 requests per 10 seconds). The app's limit is shared across all your scenarios, so slow the scenario down with sequential processing, sleeps or batching.

Most likely fix: Process data sequentially.

Symptoms

Modules fail with RateLimitError or 'Error 429'; failures appear in bursts on webhook-triggered or bulk scenarios.

Why it happens

  • Instant triggers launching many parallel runs at once
  • Processing many records in a short time
  • Multiple scenarios hitting the same app account
  • More than 300 webhook requests per 10 seconds

How to fix it

Try these in order — the most common fix is first.

  1. 1. Process data sequentially

    1. Open Scenario settings
    2. Enable 'Sequential processing' so runs don't execute in parallel

  2. 2. Add delays between calls

    1. Check the app's documented rate limit
    2. Add the Tools > Sleep module before the rate-limited module
    3. Set the delay to stay under the limit

  3. 3. Retry with a Break error handler

    1. Right-click the module and add an error handler
    2. Choose Break with automatic retries
    3. Enable storing of incomplete executions

  4. 4. Batch requests

    1. Use the app's bulk or batch module where available
    2. Use an aggregator to combine items into fewer calls

This guide also covers

  • make rate limit error
  • make 429 error
  • make too many requests
  • make ratelimiterror

Still not working?

If Make keeps failing, you're not alone. See every Make problem users report or the alternatives people switch to.

Other Make errors