That’s exactly what I’m doing though. The process restarts the transaction if it failed with a system exception.
The problem stems from when even though the process has been retried 50 times (what i’ve put in), the execution will stop. At this point the robot will need to be reset, and will start over at the first page of the pdf. That’s what I want to manage.
Using work Queues is the best practice of uipath. but in your case we can go for one approach like storing the processed data in the database tables. Initital state we have to keep one logic in first run like we have to insert all the PDF paths into the database table.
For suppose for first PDF we have successfully processed we will store some data related to PDF and we will mainatin one column with flag like yes means processed blank means not processed like that.
Foe example we have received 50 PDF’s and process got failed on the processing of 35th PDF so bot reset and it will start from the init stage. In the init state we have to keep one logic like before processing the PDF’s we have to verify how many PDF got processed so bot will take only the PDF which are not processed like the entries having the flag as blank.
sharing my thought. please give it a thought. thanks.
I’ve chose against using queues for several reasons, but today I might rethink that decision for these problems exactly. Thanks for sharing your idea, but as you’ve described, it’s similar to the integrated functions of an orchestrator queue.