How to implement error handling with custom routes on Make

intermediate 8 min read Updated 2026-04-20

Quick Answer

Implement error handling in Make by adding Error Handler routes to your modules, configuring custom error responses, and using filters to direct failed executions to specific recovery paths. This ensures your scenarios handle failures gracefully and maintain data integrity.

Full Make Review

Prerequisites

Basic Make scenario creation experience
Understanding of HTTP modules and webhooks
Familiarity with JSON data structures
Knowledge of error handling concepts

Step-by-Step Instructions

Add an Error Handler Route

Right-click on any module in your scenario and select Add error handler from the context menu. This creates a new route that will only execute when the connected module encounters an error. The error handler route appears as a dashed line with a red warning icon.

Error handlers are module-specific, so add them to modules most likely to fail, such as HTTP requests or external API calls.

Configure Error Handler Module

Add a module to your error handler route, typically starting with a Tools > Set Variable or Tools > Set Multiple Variables module. Configure it to capture error details using variables like {{error.message}}, {{error.type}}, and {{error.data}} from the failed module.

Store error information in variables for later use in notifications or retry logic.

Implement Error Classification

Add a Flow Control > Router module after your error capture to classify different error types. Create multiple routes with filters like {{error.type}} = "ConnectionError" or {{error.message}} contains "timeout" to handle specific error scenarios differently.

Create Recovery Actions

For each error type route, add appropriate recovery modules. Use Tools > Sleep followed by the original module for retry logic, or Email > Send an Email for notifications. For data errors, add Data Store > Add a Record to log failed items for manual review.

Implement exponential backoff by using increasing sleep durations for multiple retry attempts.

Set Up Error Notifications

Add notification modules like Slack > Create a Message or Email > Send an Email to alert your team about failures. Include error details using variables like Scenario: {{scenario.name}}, Error: {{error.message}}, Time: {{now}} in your notification content.

Use conditional filters to prevent notification spam for expected errors or during maintenance windows.

Configure Ignore Directive

Add a Flow Control > Ignore module at the end of successful error recovery routes. This prevents the scenario from showing as failed when errors are properly handled and resolved. Configure it to continue execution normally after error recovery.

Only use Ignore after you've properly logged and handled the error to maintain audit trails.

Test Error Scenarios

Create test conditions to trigger errors intentionally, such as using invalid API keys or unreachable URLs in HTTP modules. Run your scenario and verify that error handlers execute correctly, notifications are sent, and recovery actions work as expected. Check the execution history to confirm proper error flow.

Document your error handling patterns and test them regularly to ensure they work when real errors occur.

Common Issues & Troubleshooting

Error handler not triggering when module fails

Verify the error handler route is properly connected to the failing module with a dashed line. Check that the module is actually producing errors and not just empty results, which don't trigger error handlers.

Error variables showing as empty in handler modules

Use the correct error variable syntax like {{error.message}} instead of generic error references. Map the error data properly in your error handler modules and test with actual error scenarios.

Scenario still showing as failed despite error handlers

Add a Flow Control > Ignore module at the end of your error handler routes after successful recovery. This tells Make to treat the handled error as resolved.

Error handlers creating infinite loops with retries

Implement retry counters using Data Store modules to track attempt numbers and add filters to limit retry attempts. Use {{attempts}} < 3 type conditions to prevent endless retries.

Prices mentioned in this guide are pulled from current plan data and may change. Always verify on the official Make website before purchasing.

Visit Make View Make Pricing