RateLimitError and 429 in Make.com

Updated 2026-08-01

Make.com reports RateLimitError or an HTTP 429 when something in the chain refuses more requests for a while. The scenario fails or retries depending on your error handling. Here is how to read it without guessing.

Who is rate-limiting you?

429 can come from Make itself (operations / connection limits on your plan) or from the third-party API behind a module (Google, HTTP, Slack, etc.). The module name and error body usually say which.

A scenario that runs every minute against a strict API will hit this sooner than one that runs hourly with fewer bundles.

What to check first

Note which module raised the error and whether the message mentions Make operations, a connection, or the remote API.

Slow the schedule, reduce bundle volume (filters, less aggressive search modules), and check the app's own quota dashboards when the error is clearly from that API.

Retry / Break error handlers can help for transient limits; they do not fix a schedule that permanently exceeds a hard quota.

Paste the error for a sourced diagnosis

If you still have the execution log, use the free tool — Make's docs only, every claim linked, or an honest refusal when coverage is missing.

Diagnose this error free →

Example you can try: RateLimitError: 429 Too Many Requests. My scenario runs every minute and started failing on the HTTP module this morning.

Official Make documentation

FAQ

Is RateLimitError the same as OperationsLimitExceededError?

Related family, different signal. Operations limits are Make-plan accounting; RateLimitError / 429 is often the remote API or a connection throttle. Read the exact code in the log.

Will making the scenario run more often fix it?

No — that usually makes 429 worse. Space runs out or process fewer items per run.

Related guides

Eviverse is independent and not affiliated with Make. These guides are original explanations with links to Make's public Help Center — not republished documentation.