Difference b/w MaxRetryNumber of Config V/s Max#Retry of Queue?

Learning Hub
1

Which retry number takes precedence in these scenarios?

MaxRetryNumber in Config =0 and Max#Retry in Queue =1 /Auto Retry= OFF.
MaxRetryNumber in Config =2 and Max#Retry in Queue =1 /Auto Retry=OFF
MaxRetryNumber in Config =1 and Max#Retry in Queue =2 /Auto Retry=OFF
MaxRetryNumber in Config =2 and Max#Retry in Queue =2 /Auto Retry=OFF
MaxRetryNumber in Config =2 and Max#Retry in Queue =2 /Auto Retry=ON
MaxRetryNumber in Config =2 and Max#Retry in Queue =1 /Auto Retry=ON
MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON

2

In the default REFramework using queues, if you set MaxRetryNumber to anything higher than 0, the workflow will retry the transaction that number of times. If it is set to 0, the Auto Retry mechanism in Orchestrator will be used instead.

If you’re using anything aside from a queue item as the transaction item, the number of retries is whatever MaxRetryCount is set to.

3 Likes
3

Sorry, I wanted to know the outcome in each of the above usecases.

4

MaxRetryNumber in Config =0 and Max#Retry in Queue =1 /Auto Retry= OFF - Does not retry
MaxRetryNumber in Config =2 and Max#Retry in Queue =1 /Auto Retry=OFF - Retries 2 times
MaxRetryNumber in Config =1 and Max#Retry in Queue =2 /Auto Retry=OFF - Retries 1 time
MaxRetryNumber in Config =2 and Max#Retry in Queue =2 /Auto Retry=OFF - Retries 2 times
MaxRetryNumber in Config =2 and Max#Retry in Queue =2 /Auto Retry=ON - Retries 2 times
MaxRetryNumber in Config =2 and Max#Retry in Queue =1 /Auto Retry=ON - Retries 2 times
MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON - Retries 2 times

2 Likes
5

very useful

6

Hi,
Thanks for this thread.
Based on your reply, looks like retry is based on Config file even queue value is available. So, is this scenario only for a non-queue item based transaction.?

Thanks

7

Yes for non queue based ,
we need to set up retries for transaction . So for that we use this max retry number in config file

@JayakumarSanthanam

Hope it helps you

Nived N :robot:

Happy Automation :relaxed: :relaxed:

8

Hi,
For a queue based, if value exists in both config and queue level, which one would be used for retry count.
Thanks

9

Good day! May I reconfirm this last scenario please?
“MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON - Retries 2 times”

Should the Retries be 3 times instead of 2? Thanks much!

10

With the REFramework, the retry count in the queue only gets used if the config retry count is set to 0. Otherwise, it uses the config setting. In the case of “MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON - Retries 2 times”, it would therefore retry 2 times.

2 Likes
11

I didn’t get,
As per my understanding if,
uses the config setting. In the case of “MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON - Retries 6 times”

12

Generally what happens, “MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON
When the bot runs for the first time bot will attempt to process the transaction up to 2 retries locally as we have set “MaxRetryNumber in Config =2, If the transaction ultimately fails after all ReFramework retries, Orchestrator will requeue the transaction and retry it up to 3 times before changing the queue status “Failed”. So, (1 initial attempt + 2 max config retry + 3 max queue retry) = 6 Total Attempts.