We have recently migrated one of the process from on prem to cloud orchestrator.
It has 1 dispatcher and 2 performers.
Dispatcher : Running Fine
Performer 1 : Running Fine
Performer 2: Is having issue
I am seeking your help in resolving from all of you to handle the execution of two performer in cloud as the configuration is different in On Premise
Performer 1 runs on windows Servers A with User X
Performer 2 runs on windows servers B with User Y
We are not able to provision the server B with User Y in cloud orchestartor
add user y as a robot or attended user. assign user y and the machine template to the same folder. connect server b using the machine key. make sure user y has the right roles and license. this will allow performer 2 to run.
“Enable account-machine mappings” in the tenant setting. Then, you can see the machine-robot mapping in the machine section of the folder, where you can map your machine to a specific robot user.
There was an issue running the performer process on multiple machines, as each machine was linked to a specific robot user. Since the performer process is queue-based and the queue trigger was tied to a specific machine, it didn’t utilize other available machines to process queue items.
The dispatcher process worked without issues because it was time-based and mapped to a specific machine during trigger setup.
To resolve this, account–machine mapping was enabled at the tenant level, and each machine was mapped to its respective bot user.
