Hi All,
How maxretry queue will work in reframework and how Queue state would change in orchestrator and flow in reframework?
Could you please explain with the detailed flow?
Thanks in advance!!
Pavan.
Hi @pavan_kumar,
The MaxRetry property is the number of times a queue transaction is retried after an Application Exception. Let’s say your automation uses the calculator but during the execution the robot was unable to find the calculator, the process will throw an application exception, in the Orchestrator you’ll see the transaction as “Retried” and a “new” transaction will appear to retry the process.
That’s pretty much how it works. Let me know if it helps.
Edit: You can check more information here: Orchestrator - Managing Queues in Orchestrator
Juan P.
Hi @pavan_kumar
You can specify the Retry count when creating the Queues in Orchestrator or you can specify it in the Config file. The Retry count inbuilt in MaxRetryNumber is 0, you can give the Count based on your requirement.
There are 7 Queue states and 4 states in REFrameworks.
→ At first all queue items are in New State.
→ In Initialization state the Config file reads and Application is launched
→ In Get Transaction state it get each Queue item and change it to state to Inprogress.
→ If the Queue item got success in the Process state then the queue item state is set to Success in Set Transaction workflow.
→ If any business or system exception (application exception) occurs in Process Transaction State the queue item status updates to Failed
→ If user force stop the executing bot from Orchestrator the Queue item will be in InProgress state after 24 hours it will be updated to Abandoned
→ Retried - If the queue item failed with an System exception (application exception) and was retried. After the Robot finishes retrying the item, the status changes to Failed or Successful, according to your workflow.
→ If anybody is deleted manually in the Queues in Orchestrator then it will be updated to Deleted state.
Note : If you give retry count in Config file and Queues in Orchestrator, the bot will consider the retry count in Config file first, if it is 0 then only the bot will consider the retry count in Queues in Orchestrator.
Hope it helps!!