In this categoryAutomation · 38
- How to Self-Host n8n with Docker for AI WorkflowsStart
- How to Extract Structured Data from PDFs with n8n
- How to Add OpenAI Credentials to n8n
- How to Connect Anthropic Claude as the Model in n8n Workflows
- How to Build an AI Messaging / Chatbot Automation (No Code)
- How to Build an AI Agent with Tools in n8n
- How to Build an n8n Workflow That Summarizes New Emails with AI
- How to Build a RAG Chatbot Over Your Docs in n8n
- How to Auto-Classify and Route Support Tickets with AI in n8n
- How to Schedule Daily AI Content Generation in n8n
- How to Extract Structured Data from PDFs with AI in n8n
- How to Add Error Handling and Retries to n8n AI Workflows
- How to Transcribe and Summarize Audio with AI in n8n
- How to Summarize Incoming Emails with AI in Make.com
- How to Auto-Classify Support Tickets with AI in Make.com
- How to Turn RSS Headlines into AI Blog Drafts in Make.com
- How to Build an AI Telegram Chatbot in Make.com
- How to Answer Questions from Your Docs with AI in Make.com
- How to Auto-Transcribe Audio Files with Whisper in Make.com
- How to Extract Invoice Data from PDFs with AI Vision in Make.com
- How to Generate Images from a Spreadsheet with AI in Make.com
- How to Run AI Sentiment Analysis on New Reviews in Make.com
- How to Auto-Translate Content into Multiple Languages in Make.com
- How to Handle AI Errors and Rate Limits in Make.com Scenarios
- How to Build Your First Zap with an AI Step
- How to Use Your Own OpenAI API Key in Zapier
- How to Auto-Summarize Form Submissions and Post Them to Slack
- How to Auto-Generate Social Media Captions From New Blog Posts
- How to Extract Structured Data From Emails Using a Zapier AI Step
- How to Call the Claude API From Zapier Using Webhooks
- How to Build a Simple AI Chatbot with Zapier Interfaces and Tables
- How to Build a Multi-Step AI Research Agent in Zapier
- How to Auto-Categorize and Route Support Tickets with AI and Paths
- How to Cut AI Task Usage in Zapier With Filters and Formatter
- How to Debug AI Steps in Zapier Using Zap History
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.
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.
| Symptom | Likely cause | Fix |
|---|---|---|
| 429 error | Rate limit hit | Break directive with retry |
| Timeout | Slow model response | Retry with longer interval |
| Parse JSON failed | Model returned extra text | Strip fences, then Resume |
| Empty result | Bad or blocked prompt | Ignore 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.
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.
Error handler: Break
Number of attempts: 3
Interval between attempts: 5 minutes
Scenario settings:
Sequential processing: On
Allow storing of incomplete executions: OnStep 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.
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
25:00
138:00
72:00
55:20
13:00
120:00New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.