upload a queue to orchestrator with one robot. Then the second one starts working. When it is interrupted, e.g. at stage 2, after restarting it starts from the first stage, although the first item in the queue is successful. The second item is in processing, and the robot starts processing the third one, although it should continue with the second one in queue and second in algoritm but it starts again first. please help.
Hey @mzlota
You should implement comprehensive try-catch blocks in your workflows to catch exceptions. In the catch block, use the “Set Transaction Status” activity to mark the item as “Failed” if an error occurs, which allows Orchestrator to handle retries as configured.
In Robotics Enterprise Framework you have implemented this mechanism.
Hey @pikorpa, Thanks for your answer. I used the standard Robotics Enterprise Framework solution from UiPath, but it still happens. Could you tell me what part you are talking about?
Mzlota,
In Interrupted you mean System exception in stage 2 or Bot machine shut down while process running.
I’m writing my first queue robot. while testing it, if I notice any error in the second stage, I stop it. I change something, and when restarted, the robot starts the third stage instead of continuing the second one, which is “in process” in the orchestrator.
Hi, the robot retrieves only items from the queue with the status ‘New.’ Therefore, if you interrupt an execution during transaction processing, the item will remain in the ‘in progress’ status, and it won’t be processed further.
Thanks.
What if there is an error, then the robot starts over when I restart it?
@mzlota
Try to trigger an error in the debug mode and see how your flow behaves. In REF any exception should go through the ‘set transaction status’ workflow
Why does your process need to be restarted after an error?
Try to use ‘retry’ on the failed queue item.
Please describe in more detail how your process works.
Welcome to the community
Only new state items are picked by default and in progress items change to abandoned if left in that state for 24 hours
And whenever new transaction is taken the transaction starts from the start and not from in between
Cheers
Hi Mzlota,
Not sure what you mean by I Stop it. If there is an error at any stage Reframework will handle it.
Only the Queue items with New status will be picked by Get Next Transcation activity. If process face system exception in any of the stage it will be marked as failed as per REframwork. if you enable Retry in queue or in config file a new replica of the Queueitem will be created but it will be only processed aft completion of all Queueitems.