Process Suggestions

[Shoba]

Hi Team,

I have scenario where we have application numbers for which we have to go to a portal and enter this application number and keep launching the portal after every hour and check the status. If status is approved, we extract approval information and need not check for the next time.
Please give your valuable Suggestions.

[MohammedShabbir]

You can use Dispatcher–Performer design with Queues, and this is the approach UiPath recommend. This model provides a clean, scalable, and retry-friendly structure for your requirement.

Dispatcher simply reads all the application numbers from the input source (Excel, Database, API, etc.) and adds each of them as a separate Queue Item it, only prepares the data and pushes it into Orchestrator.

Performer takes each Queue Item, opens the portal, and checks the application status. If the status is Approved, it extracts the approval data and completes the transaction. If the status is still Pending, the bot does not fail or retry immediately. Instead, it uses the Postpone property to reschedule the same Queue Item to run again after one hour.
Use Postpone activity and postpone by 1 hr. or in Set Transaction Status, set to new. This pushes the same transaction to the future, so it will not run until the postpone time.

This allows the bot to Avoid infinite loops, avoid wasting time, Check only every 1 hour, Handle thousands of applications smoothly.
Activities - Postpone Transaction Item
Activities - Set Transaction Status

By splitting the solution into Dispatcher and Performer, and using Queue Postponement, the process becomes scalable, efficient, and easy to maintain. Each application is rechecked only at the scheduled interval, and processing automatically stops once approval is received. This design ensures reliable monitoring with minimal resource usage.

Dispatcher/Performer - use cases and advantages - Help / Something Else - UiPath Community Forum

If helpful, mark as solution. Happy automation with UiPath