Make: RateLimitError
Last verified
RateLimitErrorWhat it means
Make raises RateLimitError when a module makes too many requests over a time period to an app's API. It corresponds to HTTP 429 Too Many Requests, and the limit belongs to the third-party app, not to Make. Make's error-handling overview names RateLimitError and ConnectionError as the most frequent errors in running scenarios.
Default behavior depends on the scenario type and the "Store incomplete executions" setting. For a scheduled scenario without incomplete executions, Make pauses scheduling for 20 minutes. With incomplete executions enabled, Make stores the run and retries it automatically with exponential backoff. Instant (webhook) scenarios rerun the execution with backoff.
What is not wrong: your data and your connection. The volume or pace of requests is the issue.
What it looks like
RateLimitError
[429] Too Many Requests
Sleep before the module: 60 s / allowed requests per minute = delay per bundleWhy it happens
- An iterator sends many bundles to the same API module in quick succession.
- Several scenarios share one connection and its quota.
- Scheduling is more frequent than the app's limit allows.
- The app has a daily quota that has been used up.
How to fix it
- Check the app's API documentation for its rate limit and quota.
- Enable Store incomplete executions in scenario settings so failed runs are retried automatically instead of lost.
- Add a Sleep module before the rate-limited module (up to 300 seconds) sized to the limit, for example 6 seconds for 10 requests per minute.
- Reduce bundles per run, or use the app's bulk endpoints via aggregators.
- Spread schedules so scenarios sharing a connection do not run together.
How to stop it recurring
Design scenarios around the app's published limits from the start: batch requests, cache lookups in a data store, and keep incomplete executions enabled. Generic retry guidance is in HTTP 429.
Official documentation: help.make.com/fix-rate-limit-errors. See all Make error messages or the Make limits and quotas.
Related errors
Definitions
- Make (formerly Integromat)Make (formerly Integromat) is a visual automation platform that connects apps and designs complex workflows us
- Error HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, inc
- Rate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given
- Retry LogicRetry logic is a fault-tolerance pattern that automatically re-attempts failed operations with configurable de
Quick answers
What does "RateLimitError" mean in Make?
Make raises RateLimitError when a module makes too many requests over a time period to an app's API. It corresponds to HTTP 429 Too Many Requests, and the limit belongs to the third-party app, not to Make. Make's error-handling overview names RateLimitError and ConnectionError as the most frequent errors in running scenarios.
How do I fix "RateLimitError"?
1. Check the app's API documentation for its rate limit and quota. 2. Enable Store incomplete executions in scenario settings so failed runs are retried automatically instead of lost. 3. Add a Sleep module before the rate-limited module (up to 300 seconds) sized to the limit, for example 6 seconds for 10 requests per minute. 4. Reduce bundles per run, or use the app's bulk endpoints via aggregators. 5. Spread schedules so scenarios sharing a connection do not run together.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.