How to configure the retry functionality to my desired behavior?

A bot basing on project requirement designed in such a way that :
During system exception: retry transaction
During business exception : end process
During sucess: end process

Now queue retry has been set in orchestrator to 1 (both max retry & max consecutive systen exception retry in config is set to 0)

And the whole process works in basis of queue trigger (meaning 1 job = 1 transaction item)

So the need is if a job is running and system exception occurs, it should retry the item once and no matter whether success/failed by system exception again it should stop that particular job. But what’s happening is it if system exception occurs the job is retrying the transaction (and let’s say again system exception occurred) then the same job taking the next available transaction item instead of ending process.

Any ideas what could be wrong here

@Kakooza-Allan-Klaus

I believe the bot is not designed to end when sucessful…Ideally if you are using re framework then when a Business exception occurs or when there is a success item it picks next item…and as one retry is given…and when the second time system exception occurs it moves to getting next item only…

If you have modified RE then please show to find the error or check the conditions you have given for transition

If you set max consecutive system exceptions to 2 then when the second time system exception occurs in a row then the bot would end

Hope this helps

Cheers

1 Like