I need to read huge data from application from different screens and need to compare data at the end. For now updating data in excel after reading each screen.
Q1:Instead of updating extracted data to excel from each screen can we add data to queue in Data table format?
Also,
Q2: if the queue failed in between in any screen bot should resume reading data from that particular screen.
there is no option to update the queue item..options you have are add output when the item is successful or analytic data …when failed you cannot add output , but can add reason …again here datatable cannot be added directly, you need to serialize it and then add ..ideally writing to file or so would be ideal rather than queue
there is no functionality as such…one way you can implement is explained in the below thread..also instead of asset if you are adding one more queue item for running again then in queue items itself you can add the step number..by default it can be 1 …
You cannot add datatable directly, As per UiPath design, a queue item can contain only JSON-serializable data like strings, numbers, arrays, dictionaries.
You can Convert each row to a Dictionary / JSON object and add one queue item per row.
Also, can serialize the DataTable to JSON string and store it in SpecificContent.
Yes, If the bot fails in between, it can resume from the same screen when you design it. You can track Queue Item status ,also store last processed screen/record in Asset / DB / File.
Then on restart, read the last saved state and resume from that screen.
Q1: Instead of writing each screen’s data directly to Excel, you can design the process to push every extracted row into an Orchestrator Queue. Each queue item can represent one row of your DataTable, which makes the process more scalable and transaction-based.
Q2: To handle failures and resume from the exact screen, you should use transaction-based processing. Each screen’s data extraction becomes a separate transaction in the queue. If the bot fails in between, Orchestrator marks that transaction as failed, and when the process is retried, it will continue from the failed transaction without reprocessing earlier ones. You can also configure retry mechanisms or use checkpoints so the bot knows where to resume.
If helpful, mark as solution. Happy automation with UiPath