Solve Any Make.com Error In Minutes

[@fatalbot]

I enjoyed every piece of the video ❤ The Slack notification is probably better in a channel so your team can swarm on it. In my case, I’d track issues as tasks with adue date. For 100-199 errors, could be added to one weekly task but critical error should be reviewed right away.

[@jonocatliff]

Thank you very much! 100%, I'd put it into a group channel so that anyone on the team can deal with it asap. Thanks for the comment :)

[@AlexProton-ij3uh]

Thank you Jono, what is the best stop to create the Slack module that notifies you when an error arises? Do you do it after every critical module or is there a way to create one slack module for a whole flow?

[@jonocatliff]

Hey Alex, great questions. To my knowledge, you'll have to set up a separate Slack module for each error handler. Personally, I just set up slack message error handlers on critical messages. I'll give you two examples: 1. After a sales call, my sales team will automatically send a contract/invoice through Make.com => PandaDoc. If there's an error here, the document won't be generated and they can't do their job properly. This is something that I want to be notified about immediately so I can solve this. Down time here could be lost money for me 2. I want to automatically track analytics for leads in a dashboard like Looker Studio. Sometimes, in rare cases, leads are entered into the CRM wrong, or don't contain some sort of information, resulting in an error. I would just ignore a warning like this. In a perfect world, I would get notified about everything and fix it all. But I believe in the 80/20 rule, where I want to allocate my time to the highest leverage tasks that will deliver me the most results. Hope this helps!

[@AlexProton-ij3uh]

@@jonocatliff amazing response Thank you!! You are basically choosing flow parts where artifacts such as a report or invoice are outputted. I think, the best approach is it to observe the error incidents and identify patterns/trends to apply 80/20 rule. Thanks again for sharing your knowledge and your amazing tutorials.

[@jonocatliff]

Awesome, no worries! Thanks for always watching and commenting, really appreciate it :)

[@softreviewed]

Suppose if I have two image generation module if the first one fails I want to retry it three times then I want to pass it to the second image generation module if 1st one fails. With the break error handler this stops the execution is there any way to actually automate the process?

[@jonocatliff]

Hey, this might be a bit tricky to set up. You can have a break error handler on the image generator, which you mentioned would try the module three times. However, what might be a better bet is to have a error route where you wait 15 minutes, try it again, then move onto the next image generator, and so forth, and recreate the rest of the scenario from there. If the rest of the scenario is too long, you can break the scenario into two workflows, where you connect them from HTTP modules to webhook modules so you don't have to built the scenario out the same way for two paths. Hope this helps :)