One of my clients recently got a timeout error in a Google Sheets module (see screenshot below) in one of their flows. I troubleshot it by adding a “Break” error-handling module in order to prevent this from happening again.
This got me thinking about what the best practice for error handling is. Personally, I don’t like to add error-handling modules whenever possible as, in my opinion, they just make a flow a lot heavier for no particular reason – I use Make on a daily basis and I rarely get API timeout errors.
That being said, I want to add error-handling modules to flows when they can help clients avoid spending time on handling error notifications.
This could be intermittent server issues on the external service.
I suggest a sleep module followed by a clone of the current module, and then a Resume directive.
Handle errors so scenarios don’t stop.
You might want to add some error handling to your modules to handle exceptions, so the failing module(s) can automatically be retried or ignored. By handling any errors by adding a “Error handler” to the module, the scenario won’t throw an error and get turned off.
Error directives can only be added to an error handler route.
If you’ve changed the Google Sheet that was already set in your scenario, please ensure that you refresh the module to update the fields accordingly. Double-check that all fields and filters are configured properly after making any changes. This can often resolve issues like ESOCKETTIMEDOUT.
Best regards, Msquare Automation Platinum Partner of Make @Msquare_Automation
