hello everyone,
i am using the reframework with orchestrator queue to automate a process.
I have seen that in the event of a system exception, and with queue retry set to orchestrator 2, it recreates a new queue item but puts it at the end.
I would instead need to retry the same item immediately after the system exception. Is it possible to do this? If so, how?
Thank you in advance
Then instead of using queue retry mechanism…you can have your own retry mechanism by adding a specific content with retry value…and when a system exception occurs then check if the retry number is greater than maximum number…if not add the queue item back and increase the retry number value by 1 and while adding make sure to set the priority to high…so that this item is picked up first …if max retry count is reached then do not add item to queue
Here the assumptiions is initially you have all queue items set to normal priority
Cheers
Hi @Kumar802 I think you can disable Auto Retry in Queue and set your own retry mechanism inside REF.
You may include Add Queue Item with a higher prirority in case the transaction fails.
It’s just a simple idea. Hope it helps.
Hi @Kumar802 ,
You can put the process workflow inside Retry Scope, this way you can immediately retry if any failure occurs.
In case of any confusion, pls let me know.
Thanks for the reply. I’m using the reframework.
I’ve done some tests but I can’t implement the turn on the same item in case of system exception.
Would you happen to have an example workflow?
yeah you would need to modify it a bit.
@Anil_G 's approach will surely help you.
This is how you implement. In the system exception catch block of process transaction state
REExample.zip (947.6 KB)
cheers
thank you,
in this case though, going through the set transacition status xaml first, doesn’t it still create me an item in retried status and consequently twice the same item?
It would not create as retried as item is not automatically retried from queue retry mechanism…you will see the old item as failed only…
This is a retry mechanism that yoi are trying to do manually
Hope this helps
Cheers
so I set the retry in the queue to zero and implement the add queue item in the system exception as shown by you, without making any changes to the set transaction status, correct?
Yes…correct…
So auto retry in queue will be zero…this mechanism will take care of retry and yes no change in set transaction status…it still does the same work as needed
Only this you need to make sure is when you are adding thw queue item for the first time then also you have to include retrynumber in your specific content and it should be set to 0 by default
Cheers
Hi @Anil_G
last question: when I load queued items(in Init state), I need to create a “retrynumber” tag and initialize it to all with 0 correct?
Yes …when you are adding for the first time retrynumber will be 0…in the item collection you just need to add retrynumber on left and 0 as the value
Hope this helps
Cheers
