Fix “RateLimitError” / 429 Too Many Requests in Make.com
What this error means
The app's API allows only a certain number of requests in a time window. When a scenario sends more — usually because an Iterator fires one request per bundle very quickly — the API answers with HTTP 429 and Make reports a RateLimitError.
Common causes
- An Iterator or a search sends hundreds of requests in a few seconds.
- Several scenarios use the same connection at the same time.
- The scenario runs too often (every minute) for the API's limit.
- A retry loop immediately re-sends requests that were already limited.
How to fix it
- Add a Break error handler to the module with retries enabled and a delay between attempts — Make will retry the bundle later.
- Slow the loop down with a Sleep module after the request when you process many bundles.
- Send data in batches if the API supports bulk endpoints (one request with many records instead of many requests).
- Run the scenario less often, or split the work across schedules, and check the API's documented limits.
❌ Breaks
Iterator (500 items) → HTTP request ×500 in seconds → RateLimitError
✅ Works
Iterator → HTTP request (Break handler: retry, delay)
→ Sleep (1–2 s)💡 Pro tip: Check the response headers of the 429 — many APIs say how long to wait (often a Retry-After header). Use that value for your delay.