What is your goal?
If an automation in Make stops working because something goes wrong, how can I find the problem and make sure the automation continues working properly?
You can start here.
A good approach in Make is to use error handlers around the modules that are most likely to fail. You can then choose whether the scenario should retry, ignore the error, or route the error to a separate notification/logging path.
For troubleshooting, I’d also check the scenario’s execution history because it usually shows which module failed and the error returned by the API or service. For important automations, I’d add an error route that sends the failure details somewhere like email or Slack, so you don’t have to discover the problem manually. Once you know the failure is temporary, a retry strategy can help the scenario continue without requiring manual intervention.
I would suggest learning error handler and getting familiar with History tab in Make.
My go-to error handler when I think something will eventually go wrong is the Break module.
This stores the error without the possibility turning the scenario off - but you’d need to know where to put it.
Here is a documentation from Make: Error handlers - Help Center
Getting familiar with the History tab in Make should tell you where to find the problem.
Here is a documentation from Make: Scenario history - Help Center
You can find the problem quickly by looking at the task history. You can then look for the one that errored and see the layout of the task similar to the scenario builder which will show the route it took and whether that module ran successfully, you can see which one errored as well and click on it to see what the cause of that error was, which will help in diagnosing the issue.
I would strongly suggest error handlers as they are a great way to improve the efficiency of your scenarios and make errors less likely to halt an entire workflow and prevent the scenario from turning off. The best thing to do when building or finalizing your workflow is ask yourself with each module how critical is an error and what should happen if this module were to throw an error. While we usually look at more critical modules you can add an Error handler to every module if you wish. Is an error something you can just ignore or is it something that needs to take another route and be rectified. This can determine whether or not you use the Skip error handler or some of the others. Note that you can add any other Make module as an error handler followed by any of the other error handler specific actions. Another exciting one is the Resume handler which will allow you to substitute values that you would have retrieved from your original module back into the main flow and continue. These can be either default values or values retrieved by a module in your error route. You can read more about error handlers here: Resume error handler - Help Center