REFramework Retry functionality

Struggling with the REFramework functionality around Retry (studying for the Advanced Developer exam).

From what I can tell the Retry functionality uses the Queue setting if the Item is a Queue Item regardless of what the Config file has. So for example:

Transaction Item is a QueueItem
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 1 time
MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON - Retries 2 times

Transaction Item is not a QueueItem
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

Taking in mind what you just published.
Then this is not wrong?

Transaction Item is a QueueItem
MaxRetryNumber in Config =2 and Max#Retry in Queue =3 /Auto Retry=ON - Retries 2 times

@Luis_Jose_Rada and @jeremy_rank - the MaxRetryNumber is first grabbed from the config during the init state. It then possibly overwrites that amount in your config dictionary during the Process Transaction state using the GetQueueMaxRetries workflow.

If the TransactionItem is a queueitem variable, the GetQueueMaxRetries workflow will check the MaxRetry property of the queue and overwrite the MaxRetryNumber in your dictionary (NOTE: It overwrites the dicitonary used in the process, it doesn’t overwrite your excel/json itself). If it is not a queueitem variable, it doesn’t overwrite and exits the GetQueueMaxRetries workflow

@Dave Thank you. So the important thing is that it is more relevant if we are using a Queue Transaction the MaxRetry property of the queue than the MaxRetryNumber in the Config File.

Correct

1 Like