AutomationIntermediate

How to Handle AI Errors and Rate Limits in Make.com Scenarios

Add retries, breaks, and fallbacks so your AI scenarios survive rate limits and bad responses without breaking.

9 minIntermediate

AI modules fail in predictable ways: rate limits, timeouts, and malformed output. A scenario that ignores this stops at the worst moment. This guide adds the error handling that keeps your AI flows running unattended.

  • An existing Make scenario that calls OpenAI
  • A Make.com account with scenario editing access
  • A place to log failures, such as a Slack channel or a sheet

Step 1: Understand the common errors

The two you will see most are HTTP 429 (too many requests, a rate limit) and a JSON parse failure when the model returns prose instead of clean JSON. Each needs a different response: retry the first, sanitize or skip the second.

SymptomLikely causeFix
429 errorRate limit hitBreak directive with retry
TimeoutSlow model responseRetry with longer interval
Parse JSON failedModel returned extra textStrip fences, then Resume
Empty resultBad or blocked promptIgnore and log

Step 2: Add a Break handler for rate limits

Right click the OpenAI module and choose Add error handler, then add a Break directive. Break tells Make to wait and retry the failed bundle automatically. Set the number of attempts and the interval between them.

Make.com - error handler menu
Right-click OpenAI module
> Add error handler
[ Break ] retry on 429 / timeout
[ Resume ] continue with a fallback value
[ Ignore ] skip this bundle, keep going
[ Commit ] stop and save what is done

Step 3: Configure retry settings

Open the scenario settings and enable Sequential processing so retries do not pile up. On the Break handler set retries to about 3 and the interval to a few minutes, which clears most short rate limit windows.

Break handler settings
Error handler: Break
  Number of attempts: 3
  Interval between attempts: 5 minutes
Scenario settings:
  Sequential processing: On
  Allow storing of incomplete executions: On
Slow down before you hit the wall
If you process many items per run, add a Sleep module of a second or two between AI calls. Pacing requests prevents most 429s in the first place, which is cheaper than retrying them.

Step 4: Add a Resume fallback for bad output

For parse failures, add a Resume directive on the Parse JSON module. Resume lets the scenario continue using a default value you supply, so one malformed response does not kill the whole batch. Route those cases to a review log.

Step 5: Log every failure

On the Ignore or Resume path, add a Slack or Sheets module that records the input that failed and the error message. You want visibility into what slipped through so you can refine the prompt later.

Make.com - execution history
Run 14:02 attempt 1 -> 429 rate limit
Break: waiting 5 minutes...
Run 14:07 attempt 2 -> success
1 bundle resumed with fallback, logged to #ai-errors
$

Result: a resilient AI scenario that quietly retries rate limits, recovers from bad responses with a fallback, and tells you about anything it could not handle, instead of silently stopping.

Watch related tutorials

Tags
#make.com#error-handling#rate-limit#retry#reliability