So for the first one I am able to start an unattended process, but for the second one I can’t because is stuck in Pending state forever. Is working only after I manually disable the first robot, so that second one can have the license. I thought that 1 NonProduction license can be shared between multiple robot accounts, isn’t it?. It seems that is not working.
I understand that, but I don’t need the processes to run in parallel, is it ok to run one after another, but it doesn’t work at all, the second process remains in Pending state, since the first robot does not release the license for the second robot.
is very strange because for classic robot this worked…8 robots could share same license without me having to manually disconnect any of them…during the night we had multiple processes scheduled to run on same machine with different robots and everything worked fine, but if we want to migrate to modern folders this is not possible anymore
classic robots on same standard machine, all 8 robots can run processes on that machine one after each other:
How is modern folders a better thing when it comes to license consumptions? It seems that now I have to get a license for each user
This is how it was before, according to their documentation, but now for modern folder is not the case anymore: For example, if on a machine with 5 Robots, you assign only 3 runtimes, it means only 3 licenses are consumed. If you execute 5 jobs or schedule all the Robots on that machine, the following occurs:
1. 3 jobs are executed on the first 3 licensed Robots; 2. the remaining 2 unlicensed Robots are placed in a pending state; 3. the first 3 Robots release their licenses; 4. the remaining 2 Robots are licensed and they execute the assigned jobs.
I think you are not properly signed out from both the users. License needs to be free in order to allocate it to users. If you simply disconnect the user session, still your session is active and license is occupied by the user.
Make sure you have “signed out” from both the users.
During the job run a session will be created if you have properly signed out. Available license will get occupied and job will start running. After the job completes session will sign-out on its own and your license will become free again. I was able to run one after the other from both users in the same machine with a single license.