How to have account-machine mapping available on Queue Trigger, so that they can run on multiple specific Robots and should not be executed on any other.
Possible Resolution/ Workaround:
- Maintain a separate folder for executing this process so that it should not have other Robots involved
- Set maximum number of pending jobs to 3
- Provide the machine template that is being connected with 3 runtimes so that three accounts can be configured simultaneously
- Once the dispatcher end and the queue-based trigger will start 3 jobs with all available account and machine mappings in that folder( since the folder is separate only these 3 Robots will be there)
- Since there are three runtimes, all three will run parallelly on the server with 3 accounts
Example: In the below scenario, the host name is same but accounts are different where only these two accounts are configured for that folder.
- In the Queue, trigger settings try to set maximum number of pending or running jobs to 3 and set execution target to any Robot account and any machine.
- If it is required to use assets and queue from different folders, use link concept to link Assets and Queue from different folders so that they can be used across multiple folders.
Queue link: Managing Queue Links .
Asset link: Managing Asset Link .