I would like to know whether it is possible to utilise e.g. 3 unattended licences across 4 virtual machines. The machines will each be running different processes and will be running at different times. I am using Automation Cloud with Modern Folders.
I spoke with UiPath support who are confident it cannot be done without manually toggling licence activation between machines but I wanted to check with the community for a second opinion. It seems to me that wanting to utilise a free licence on any machine is a pretty standard request.
If this is the case why to use another machine. You can use the any of the 3 already licensed machine.
The logic to assign/consume license is simple,
License Consumption upon Connection:
As soon as a machine is connected to the UiPath Orchestrator, it consumes a license, even if it’s not actively running any processes.
In your scenario, if 4 machines are connected at the same time, only 3 of them can be allocated licenses (based on your available license limit), while 1 remains without a license until one is freed up.
Licenses Not Automatically Released:
The licenses consumed by the machines are not released unless a machine gets manually disconnected or disconnected due to a network or system issue.
This means that as long as a machine is connected, it holds onto its license, regardless of whether it is executing any processes.
License Reallocation:
When one of the connected machines is disconnected (manually or due to any issue), the license it was holding becomes free.
Another machine that is using the same template (a configuration for virtual machines or environments) can now automatically take that freed-up license and start running processes.
Same Template Logic:
Machines using the same template will share the available licenses. When one of the machines disconnects, the freed license is automatically allocated to another machine in that group.
This is a common scenario in environments where there are more machines than available unattended robot licenses. In such cases, machines are prioritized based on connectivity rather than process execution.
Thanks for getting back to me. Unfortunately in this case it is not feasible to share the same machine but your answer is the second opinion I needed to present this back to the relevant stakeholders.