Hi Make community!
I’ve been building some complex workflows with multiple apps and steps, and sometimes errors happen mid-way, which can break the entire automation. I’m curious to know:
-
How do you usually catch and handle errors in your multi-step workflows?
-
Do you have any strategies for retrying failed steps automatically?
-
Any tips for logging errors so you can debug issues faster?
I’d love to hear your approaches and best practices — especially if you’ve found clever ways to make workflows more resilient and reliable.
Thanks in advance!
Hey @Peterparker , there are up to five erroe handlers in make. Some errors require that you use the error handlers while some require that you properly format your input data. Each error handler is peculiar to certain instances. So you determine which error handler to use depending on the situation.
Error handling in Make is pretty simple, using error handlers is the best way to do that. The most common one is “Ignore” this is true if perhaps you want the flow to continue and then just do nothing.
Personally my favorite is the “Resume” error handler. This can allow you use fallback mapping data for the important outputs you would need for future module that reference the errored module. You can also connect traditional Make modules within the error handlers path which can make this a pretty powerful tool as well.
Hello,
There is no best or preferred way of handling errors.
It all depends on the module and the type of error that can occur - how often it happens and how it impacts the scenario.
You should always analyze the best approach for your workflow needs.
Sometimes the best solution will be the break module.
On the other hand, if the API often returns code 5xx (temporarily unavailable), you can use a combination of sleep and retry of the API call with the Resume module.
Take a look at Make.com documentation - it will give you detailed information on how each error handler works. Quick error handling reference - Help Center
1 Like