I think what you’re looking for is: Concurrent User
This type of license is available for Attended and Development Robots.
A type of license that helps users that work in shifts, as licenses are consumed only when you actually want to use a Robot.
A concurrent license is consumed in Orchestrator, depending on its type, when:
the Robot is connected to Orchestrator
the UiPath Robot Tray is running (and not only while it is executing a process)
Studio is running
As a result, you can have hundreds of Robots defined on multiple machines but only use, for example, 50 licenses at a specific moment in time, as that is the maximum number of users who simultaneously connect their Robot to Orchestrator.
More info here:
As mentioned by @ovi , for unattended robots, UiPath has concurrent runtime licensing model. As mentioned by you earlier, you want to run 2 processes on same VM at different times using different robots. You can assign 1 runtime to this VM in orchestrator from “Machines” Tab and can configure 2 robots against this machine.
Sorry I may not have been clear - I don’t need to run concurrently on the one machine
As the windows users dictate what applications the user can see, I want to be able to use 4 licences, across more than 4 users, but at different times
So 1am - 1pm the 4 licences are assigned to windows users 1-4. From 1pm - 1am, the 4 licenses are assigned to windows users 5-8, thus allowing the robots to access different applications.
any update on your problem? i am also having the same situation where my customer only have 1 unattended robot but they want to share it with multiple department (diffrent windows user but on the same VM )
@ovi can you please confirm if this scenario work ? the robot will not work on the same time.
can we schedule the robot to run on UserWindows1/VM1 on 9AM, then run on UserWindows2/VM1 on 12 AM.
Any update on how to make this work? We have a two processes that can be accomodated on one machine, but need two different IDs. Compliance won’t allow one user (robot ID) to be assigned to both roles.
I have a similar scenario, where I have a need to use two different Robot Id’s on the same VDI (license). I was able to create two unattended robots in Orchestrator (2018.4.6) both with the same machine. I ran an automation on each robot on that same machine and they both ran successfully. I even ran both at the same time to ensure that Orchestrator would put the second one into pending state and it did.
