“If a transaction item in a UiPath process reaches the ‘Abandoned’ state within the Orchestrator, is it possible to process these transactions without modifying the underlying automation code? If yes, what would be the approach to accomplish this, and are there any considerations or configurations required to ensure the process handles retries effectively?”
Hi @smile_munjal Welcome to the UiPath Community Yes, it is possible to process transactions that have reached the “Abandoned” state in UiPath Orchestrator without modifying the underlying automation code.
A transaction item in a “Abandoned” state occurs when the item has been in the “In Progress” state for too long and exceeds the processing time limit (default is 24 hours) without completion.
These items cannot be directly retried from the abandoned state, but they can be re-queued manually or automatically for processing again.
Select the abandoned items and use the Re-queue option. This will create new queue items based on the abandoned transactions, which can be processed by your existing automation without changing the code.
Please find below screenshot for your reference:
Hi @smile_munjal ,
You can accomplish this without accessing the code. Simply log into Orchestrator, navigate to the Queues section, and then select Queue Items. From there, find the item with the Abandoned status, click the three-dot menu next to the item, and choose the Retry option. This action will create a new Queue Item with its status set to New.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.