I am looking for the best way possible to implement the following scenario. For the example we’ll say we have 10 VM’s with bots: 5 of them automate different actions in ProgramA, 3 automate different actions in ProgramB, 2 automate different actions in ProgramC. So, to start, each of the bots managing a particular program will be in their own Environment.
Each of the 10 different actions will have their own Queue. Queue items will be added through API calls.
So one option is to simply run each bot on each VM 24/7, constantly looking for a new item in it’s assigned queue and working them as they come in. It’s OK, but I’d like a better option, because some of these automations will probably be more used than others. So I wouldn’t want a queue to start backing up with requests that manages ProgramA when we have 4 other bots that have the same program open sitting there not doing anything because they’re already looking at only 1 queue each.
Ideally I’d like to have a new incoming queue item initiate an automation, and end when finished until the next one comes in. If possible, I’d like to allow it to initiate any available robot within a particular environment.
Is there some way within Orchestrator to… orchestrate this?