Error handling in larger scenarios, help needed. šŸ™

How To
, ,
1

Hey everyone!
I have a question related to error handling in larger scenarios.

Take for instance the scenario in the image below. (1) A trigger in Monday.com (ā€œwhen status change in subitemā€) initiates the scenario, it then (2) gets various kinds of information from the trigger item and parent item using a GraphQL query, and then (3) does different things depending on the results of those queries.

image
image760Ɨ987 91.8 KB

How would you go about creating error handlers for this scenario?

The reason Iā€™m asking is that we had an 502 error return from this scenario yesterday. Only one of the action modules (3) was affected by this.
I could of course make an error handler path for each module, specify which actions to take depending on different error codes. But that seems a bit excessive. I could optimise that a bit by creating a secondary scenario that gets called to handle the errors and call that instead, but that is still a lot of error handlers to implement.

Is it not possible to, somehow, make a catch-all for the entire scenario? I know that Blue Prism has a really nice way of handling that for instance, with what they call ā€˜bubbling upā€™. Where an error in a scenario (or section of a scenario) can ā€˜bubble upā€™ to the next up in the chain to handle the error.

For instance; Scenario A runs, and calls scenario B, when B finishes, it proceeds in A. Now if B were to return an error, A would handle the error, instead of having to make error handlers in B.

So how would you guys do error handling?

1 Like
2

Hi @LindaFuchs

Itā€™s better to include a break error handler in all Monday.com modules. This helps address potential runtime errors by retrying the operation and effectively managing any issues that ariseā€¦

Best regards,

Msquare Automation
Platinum Partner of Make
@Msquare_Automation

3

Thanks for the reply @Msquare_Automation ,
So in effect though, it still boils down to having error handlers for each and every module in a scenario?. That there is no easy way to create a ā€˜scenario-wide fallback routeā€™ in case the error does not match any error handlers that might be present on the module?