Break Error Handling for Auto Retry

How To
1

I have a massive flow and multiple routes I have break module on each Claude API step which has the same things to trigger 3 times (Break MODULE)

But I am doing something completely wrong - the scenario auto completes even though there is an error why does this happen - it should just stop and retry before completing other parts right?

Or else I am super wrong about something, thanks in Advance

image
image1084Ă—727 67.3 KB

1 Like
2

Here is a more detailed breakdown

My flow has multiple routes
Each route has Claude as a module
I am hitting Overloaded Error in the flow I want to use the Break (or any other module to first try to resolve the error before letting others proceed - I don’t want flow to complete without everything being resolved)
I think Resume Might be an option but not sure (as sometimes it does take a couple of retries)

Thanks for the help

3

Hi @akshatbahety

With error, the scenario will stop the route where it throws the error. However, it executes other routes.

Regards,
Msquare Automation - Gold Partner of Make
@Msquare_Automation

4

Hi @Msquare_Automation ,

what could be an option to resolve this?

Thanks

1 Like
5

You can stop the scenario using commit. However, it won’t retry the module. If you want to retry the module, then this is also fine. You can run the incomplete node from incomplete executions. @akshatbahety

Regards,
Msquare Automation - Gold Partner of Make
@Msquare_Automation

6

Hi @Msquare_Automation,

Thanks but is there a way to retry it automatically in case of an error as at the end the flow sends out an email and I don’t want that to happen until everything is done.

I don’t want to manually keep running it

1 Like
7

@akshatbahety

Then you can do one thing, put “set variable” at the end of each node and store the output from last module of that node.

On next route, add “get multiple variables” module first and map the variable names you added in set variable in previous node. Then set a filter, if the value from “get variable” exist, then only it should pass.

This will not run the next node unless the previous node is succesfully run. However, even if its retry, it won’t execute the next node.

Regards,
Msquare Automation - Gold Partner of Make
@Msquare_Automation

1 Like
8

@Msquare_Automation thanks a lot

Okay here is an alternate solution that I am thinking of please let me know if this works based on your experience

If I set up the break modules to run within a small interval of like lets say 1 minute each
and then execute the last route after around 5 minutes

For example in case I get 2 errors in the flow and they both keep retrying within that 5 minutes will it work out? (like would the same flow be updated with the new details or it’ll 100% create a separate record)

Please let me know if you think that works - or if you need more details

Thanks,

1 Like
9

Okay really need someone expertise to solve this

If a scenario has sequential processing turned on - it does not pause the scenario and only executes the Break Module based error once the current execution run has ended?

This just doesn’t make sense - it should stop in middle and then execute the error and then execute the other items

Is there a way to do this

Thanks

10

Hi @akshatbahety

There are ways to do but any way is not efficient as it should be as this is not the feature of make.

You can put error handler route with sleep and “Resume”. However, in this case, you will have to do this for every module, that is not efficient.

The best way seems to check for the existence of all the attachments you are sending in email before email module. If all exist, then send the email, later things that are for your database, will be done in break time.

Regards,
Msquare Automation - Gold Partner of Make
@Msquare_Automation