Power Platform Community Forum Thread Details

So I have complex requirement for PAD queuing:

Two bots
- First one utilizing legacy application with UI, Log's in to application, fetches list of cases from excel and starts handling those one by one, once finished, closes application via log off.
- Second bot get's triggered via Sharepoint list and whenever new item is added, it should be handled on priority over first bot.
So how to handle first item handling the way that it does not log off after every item processed and goes back to run queue to be checked against high priority items in that.

Ideally per my understanding the first bot should start and after finishing each item, should be able to check if in that machine run queue is high priority work queued, if yes, then log off, create for itself new run queue item and give resource for high priority item.

But so far I haven't figured out how to orchestrate that.

Adding first bot items one by one to run queue would create huge amount of unnecessary login/logoff's...

Any ideas?

Categories:

Power Automate Desktop

Assuming your second bot is also a desktop flow (because otherwise you wouldn't need to orchestrate stuff anyway), you can make your first bot run the second bot via the Run desktop flow action. Then have your second bot process all queue items in its queue every time it runs via the Process work queue items action (assuming you're using the new work queues for orchestration). When the second bot is done (even if it has nothing to process) it will come back to the first bot, as it will be waiting for the second bot to complete.

So, the idea would be somewhat like this:

Bot #1 starts
Launches the UI and logs in
Fetches the cases to process from Excel
For each case:
1. Processes the case
2. Runs desktop flow (bot #2)
  1. Bot #2 runs
  2. Processes all cases from the work queue
  3. Bot #2 ends and returns to bot #1
Bot #1 closes the UI by logoff
Bot #1 ends

You should then obviously make your cloud flows also able to call bot #2 independently, so that it can also run when bot #1 is not running. Simply make your cloud flow run it whenever it is triggered. It would get queued if bot #1 is running, but it won't fail if it has nothing to process.

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.