Seeking help with Robots and Pega Operator ID in Robot Manager v. 1
We are having some difficulty with the robot operator IDs having to be manually deleted every time OpenSpan Runtime terminates. If they're not deleted then when OpenSpan runtime starts again then it will not be able to connect through the robot manager and will immediately shut down again. This can happen, for instance, when IT pushes updates to our robotics VMs because they have to be rebooted after the updates. In a previous SR call with Pega we were advised to either manually exit OpenSpan runtime using the menu, or use the "ShutdownRuntime.exe" utility. These machines are not normally accessed by users, so the solution we put in to place is to schedule an automated procedure that would periodically run "ShutdownRuntime.exe" and initiate a reboot, shortly after the updates are pushed.
However, it appears that running "ShutdownRuntime.exe" does not fix the problem of the operator ID.
We are going to upgrade to the latest Pega and the latest Robot Manager as soon as possible, but at this time we cannot. Is there something that can be done for this problem in the meantime?
Pegasystems Inc.
IN
Hello,
Please let me know what version of Robot manager you are using. Please check if ProcessStaleRobots agent is enabled in PRPC.
Regards,
HealthFirst
US
It's version 1. Yes, "ProcessStaleRobots" agent is enabled. It's setting pyOpAvailable to false when the robot's last sign on is greater than 10 minutes. It runs every 15 minutes.
HealthFirst
US
Hi gummv1. Are you able to provide any help with this issue?
I really need to know one thing: Is there anything within Pega, either a setting that can be tweaked or a process created, to handle the operator IDs so that when robot VMs get restarted they'll be able to connect?
HealthFirst
US
It's version 1. Yes, "ProcessStaleRobots" agent is enabled. It's setting pyOpAvailable to false when the robot's last sign on is greater than 10 minutes. It runs every 15 minutes.