I am using the Community Edition and have been using the unattended bot successfully for the past few weeks. However, today my scheduled bot did not run and when I checked the Orchestrator for detail it says: “Robot Licensing Failed. There are no available licenses on the server. (#1914).” However, I checked the remote PC’s bot and it says “Licensed, connected.”
I can manually run a task on the remote PC now, however, if I run the same task through Orchestrator, it gives the error mentioned above.
I have the same problem, the robots worked until 3:00 p.m., so it stopped working. with the same error Robot Licensing Failed. There are no available licenses on the server. (#1914).
I checked the remote PC’s bot and it says “Licensed, connected.”
I also have this same problem today. It has been fine up until now, I run at least one job a day and have not changed the process.
I did notice that there is now an icon next to the process that says “requires user intervention”. None of my jobs require user interaction, even to test I made a job that just prints a line. I do not think this ever used to be there, maybe there is a bug with the platform?
Yesterday, when creating the machine, the unattended license count was not assigined and was zero count. So today, i first did delete and my robot and machine.And then i created my machine that License - Unattended Runtimes was assigned zero to one like below.
So the duplicate entries are normal when you have the robot installed in user mode (one is for the machine in service mode - it’s provisioned when you create the machine, and the others may be the robot services installed in user mode on that machine). Prior to 20.3 we had a bug - if you had multiple robot service instances on the same host, they would have all shared the same runtime pool of licenses - and that was incorrect. If you actually want them to share the same pool of runtimes, you should just install the robot in service mode.
However, we had a bug in our latest deployment that we did not release the licenses for unattended robots correctly, and we also “forgot” to show the “user mode” information in the licenses page UI.
We will (try once again) to release all the unattended licenses so this problem should fix by itself (with the first Robot Service heartbeat that comes after the fix).