What is function of the execution slots in the machine template property

Dear all,

I bit confuse about function of execution in the machine template property in the OC.
my understanding is
for example:
if I set 3 slots, only 3 robots able to run a process in the same time even you have provisioned 4 Robots.

correct me if I am wrong?

thank you,

Hi @irahmat ,

Assistant will not allow you to connect if three license already utilized, it will popup error message “No license available”.

Hi Manoj,

thank you for your answer.

let’s say you have utilized 4 Robots and set 3 slots. ignore about ‘No licenses available’
and you run a process by 4 Robots in one machine template in HD Environments

what will happen?

Not sure on this.
This is real based problem, never faced this.

Wait for others answer.



Robot service gets triggered for first three triggered process and process will run fine for three and fourth will not do any thing is what I have observed once
If we have another concurrent runtime license it will also run or it will be in pending state until the runtime is over for any of the running robot

That is if you have four processes running one machine (windows server with multiple account with three concurrent runtime license) then first three process will run and fourth one will be in pending state till runtime license is available


1 Like

Hi Palaniyappan,

my understanding same as you but let’s go to the real problem what I was facing yesterday.

what have happened yesterday, the 4 robots running at the same time.

I used the cloud Orchestrator v21.6.x

This controls the “Concurrent” runtime execution slots available to a machine. So if you have it set for 5 Slots and have provisioned 6 Robots on the machine. When you attempt to start more than 5 Jobs simultaneously the 6th job will go into a pending state until a slot frees up.



And then you can see here after I stopped one of the jobs, the pending job was picked up.

The above was done when I selected six specific robots. If you used dynamic allocation, it would show Pending allocation for the Robot and Pending for the Job State

1 Like

Hi Tim @codemonkee, thank you for your insight.

I’m facing a similar problem, maybe you can expand on this:

I have 1 machine template with 1 execution slot allocated and 2 machines connected to it. I was expecting to be able to run a process on the first machine and subsequently on the second machine.

However only the first machine actually gets licensed and doesn’t seem to release the execution slot after the job is done. The job on the second machine doesn’t get executed until the machine/license is manually deactivated.

Am I missing something? How can I execute processes subsequently on different machines with one license?

Thank you, Lukas

I believe that is intended behavior for your scenario @lukasziebold. In my example it is a collection of “Robots” on a single machine. I *think* what is happening in your case is that the UiRobot whether that is in User Mode or Service Mode needs to release the license which is done by disconnecting.

If in User Mode, this is done when a user logs off, but in Service Mode the connection is maintained while the service is running in the background which doesn’t make your scenario feasible unless you also have a process for controlling your servers/VMs, or templates.

This is backed up by the following note


  • For unattended robots, licensing is performed per allocated runtime (slot) entity instead of per user. That’s why Unattended, NonProduction, Testing runtimes are assigned at the machine level.

  • Say you have a machine template defined with 10 unattended runtimes. For each workstation connected using the key generated by that template, a pool of 10 licenses is reserved from the total number of licenses at the tenant level. A runtime is only consumed from the pool of reserved licenses during job execution. If you connect 4 machines to Orchestrator using that template, you need 40 unattended runtime licenses at the tenant level. With 25 jobs running, there are still 15 slots available for execution.

  • Unattended robots can be used in attended mode in a production environment (the user logs on to the machine) for logging/testing/debugging purposes.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.