Queue state from retried to new then failed

[Bharat_T]

In REframwork when you get an system exception it marks particular item as retried and creates new queue item then then comes for retry and then fails. How this mechanism is happening in REframework? I don’t see any activities for mark queue item as retried and creation of new queue item.
Set transaction activity is used to set success/failed but from where retried statis is getting updated?

[Anil_G (Anil Gorthi)]

@Bharat_T

When the status is set to failed…orchestrator queue takes care of setting the item to retried and adds a new item…this mechanism is not done in REF…but is taken care by the queue…that is the reqson you set auto retry in your queue…every queue item will have a property retry number…till max number is reached this behaviour is repeated by queue

Hope this helps

Cheers

[Shiva_Nikhil]

@Bharat_T

For more reference check this

Retry Mechanism in RE-Framework

Yeah, just as a simple answer… The Queue retry is a different mechanism as the REF. Essentially when a queue item changes to Failed status, Orchestrator will set it to Retried status and add the item again as New status, so your process can pick it up again. The Retry mechanism in the REF will retry the item but not trigger the Retries in Orchestrator. So let’s say you retry an item 3 times in your code then it changes to Failed, then Orchestrator will set it as Retried, and when your process p…