I have a machine template with 3 Windows servers (Citrix Environment). All 3 have heartbeats. I have set up the Template to allow 5 instances per server. I have 9 runtimes (bot accounts) assigned to the template (all 9 run when I allow 9 to run on 1 server but bad performance). 5 jobs will run on 1 server, but the other jobs will just sit in Pending and not start on another server (even if I force the host manually in the trigger). If they finish and need to restart to process new transactions, they sometimes will restart with the next batch of queue items on another server, but only on that 1 server. The other Pending jobs will never start except on the server that was first started - not even on the previously used server.
How do I get the other jobs to cascade to the other servers to run at the same time?
Cloud Orchestator
On Prem servers (UiPath 2024.10.1)
Below are the screenshots, however, this morning everything was working as I expected. Jobs are starting on all 3 machines. I guess the bots just had to get used to their new office locations.
Just a quick double-check here. Your screenshot shows that you have 17 licenses. Your MT setup would use at most 15 licenses. However, are these 17 licenses being used elsewhere? This could have caused yesterday’s problem.
There appears to be a very large time lag between the time the multiple servers are set up and the time Orchestrator starts load balancing across them. That is the only explanation for what I experienced. This is the case, at least, for our setup. Multiple machines on a template all in a Citrix environment.
