How to Configure Error Handling in Make.com
Error handling in make.com lets you control what happens when a module fails, so your automations stay reliable and easy to maintain.
This guide explains, step by step, how to set up error handling routes, apply directives, and manage notifications using the built-in tools available inside each scenario.
Understanding error handling in Make.com
When a module in a scenario fails, make.com can follow a special branch called an error handler. This branch is separate from the main data flow and is used only for dealing with errors.
The core ideas you need to understand are:
- Error handlers – dedicated paths that run only if a module encounters an error.
- Directives – rules that define how the run should continue after the error handler finishes.
- Notifications and logging – tools to inform you and track what happened when something goes wrong.
How error handlers work in Make.com
Each error handler is linked to a specific module in a scenario. You can add more modules to the error handler route, but it always starts from the module that might fail.
When that module errors, make.com will:
- Stop the standard flow for that particular execution.
- Switch to the error handler connected to the module.
- Process the error according to the directives you configure.
This design gives you precise control over how failures are handled without stopping the whole scenario unless you choose to.
How to add an error handler in Make.com
To set up an error handler, open your scenario and work directly with the module that may cause problems.
Step-by-step: Adding an error handler route in Make.com
- Open the scenario editor
In make.com, open the scenario where you want to manage errors.
- Select the target module
Click the module that is likely to fail or that you want to monitor closely.
- Add the error handler
From the context options of the module, choose the option to add an error handler. A new route appears, attached to the bottom of the module with a special icon to show it is an error path.
- Build the error route
Add any modules you need inside the error handler branch. Typical actions include sending alerts, logging data to a spreadsheet or database, or cleaning up partial operations.
You can attach different error handlers to different modules in the same scenario, allowing specific reactions to different types of errors.
Choosing directives for error handling in Make.com
The directive defines what make.com should do after it finishes processing an error in the handler route. Configuring the right directive ensures your scenario behaves as you expect when something fails.
Common error handling directives
Depending on the module and the scenario, you can choose from several directives, such as:
- Ignore – Log the error, optionally process it in the error route, then continue the scenario with the next item.
- Roll back or stop – Prevent the rest of the scenario from running, sometimes reverting partial changes depending on the modules involved.
- Resume – After the error handler finishes, continue with the next module or next bundle, skipping only the failed item.
Selecting the right directive helps you decide whether your automation should keep going or stop in response to a failure.
How to set a directive in Make.com
- Open the error handler settings
Click the error handler icon attached to the module.
- Choose the directive
Use the directive dropdown to select how the scenario should behave after the error handler runs.
- Save and test
Save your scenario and run a test to confirm that the chosen directive behaves as expected when an error occurs.
Designing useful error routes in Make.com
An effective error route in make.com should do more than just stop the run. Ideally, it should record what happened and warn the right people.
Typical modules to use in an error handler
- Email or chat notification modules – Send a quick message to your team or to yourself with error details.
- Database or spreadsheet modules – Write error information to a dedicated log table or sheet.
- Issue tracking integration – Create tickets in tools like Jira or other project systems.
- Cleanup modules – Reverse partial operations if the connected apps support such actions.
By combining these modules, you can build a robust monitoring and recovery system directly inside your automations.
Testing error handling in Make.com scenarios
Before you rely on any scenario in production, always test the error handler to ensure it works as intended.
Steps to test an error handler
- Prepare test data
Use data that is likely to trigger an error, such as invalid input or missing fields, depending on the module.
- Run the scenario
Execute the scenario in make.com and watch the run history.
- Inspect the execution log
Confirm that the failing module triggers the error handler, and that all modules in the error route execute correctly.
- Adjust directives if needed
If the scenario stops or continues in an unexpected way, update the directive and retest.
Monitoring and optimizing error handling in Make.com
After deployment, you should keep an eye on how often your error handlers are triggered and what they reveal about your integrations.
Monitoring tips
- Review run history regularly – Look for repeated errors connected to the same module.
- Analyze log entries – Use consistent fields for logged errors, such as timestamp, module name, and error message.
- Refine scenarios – Update filters, mapping, or conditions in make.com to reduce recurring errors.
Good monitoring helps you catch issues early and refine both your scenario logic and your external systems.
Additional resources for Make.com error handling
For deeper reference and specific module behaviors, consult the official documentation on error handling directly from the platform. You can learn more at the following page:
Official Make.com error handling overview
If you want expert help planning large-scale automations, scenario recovery strategies, or audits of existing flows, you can explore consulting services at Consultevo.
By using error handlers, selecting the right directives, and testing regularly, you can ensure that your automations in make.com respond gracefully to failures, stay stable, and provide clear insights whenever something goes wrong.
Need Help With Make.com?
If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.