I have been running processes on the same machine for a long time with different schedules.
Only one unattended license with Orchestrator ()
1 machine (machine_x)
3 robots (robot_x, robot_y and robot_z)
3 processes. (process_x, process_y and process_z)
The process_x is executed with robot_x at 06:00 a.m on machine_x
The process_y is executed with robot_y at 07:00 a.m on machine_x
The process_z is executed with robot_z at 08:00 a.m on machine_x
The problem is that only process_x is executed and process_y and process_z stays pending with that error ( Robot licensing error. There are not licenses available )
It is as if the license was kept in the first robot and not released.
Is it possible do “LOG OUT” without giving an Orchestrator’s error?
Since you are using the High Density Architecture for robots, this has to be done. This ensures the robot user logs out of the system once the process execution is complete.
as you mention i hope you having only one unattended robot
so what is the purpose of creating 3 robot for run your process in 1 machine
Assumption : when your process X executed 6.00am and make sure that its finish before process y starts (as you say its start 7.00am)
if like then you have enough 1 created robot and dispatch your process at the time in to same robot
form your scenario your all process (X/Y/Z) are dispatching on same time and trying wait until its jobs start the process
but you have only one license , i hope its a concurrent license (can run only one robot at a time) so all the 3 jobs cannot be dispatch in to 3 different robot cause its connect only one robot , thats why you will reseive this message
but if not, try the possibility of updating your robot or orchestrator version
if so cant you can use task windows task scheduler (but remember now is’t not recommended )
and following link having the already created component for it
you can easily do it
