Error Requesting Data From Pega, Unable To Acquire RobotInfo (Pega 7.2.2, Pega Robotics Studio 8.0.1058.0, Robot Manager 1)
We've designed a simple automation with openspan that we've configured to connect to a pega application, but whenever we try to start the Pega Robotics Runtime, it immediately closes. The runtime logs give these errors . . .
-Registering Robot step1 - Name: '5D', Queue: 'TestWG'
-Error requesting data from Pega. https://*******.pegacloud.io/prweb/api/v1/cases
-Code: InternalServerError(500), Content: System.Threading.Tasks.Task`1[System.String]
-RoboticsService.RegisterRobot - Unable to acquire RobotInfo.
-RPA mode is enabled, but robot failed to register. Runtime will shutdown.
In the CommonConfig.xml, underneath the <Servers> tag, within a <Server> tag, I have set
We have set up our pega application correctly to my knowledge, as the robotics workbasket we created is registered in the Robotics Automation Console Portal, and it contains cases. We can also pull up the fields in Visual Studio that we've specified in the relevant records within our pega application. The robot registered within the console is red and says "Robot connectivity has been lost".
Can anyone give me an idea of why the runtime is immediately shutting down after we try to start it?
(Upgrading Pega Platform and Pega Robotics Studio version is not an option)
Unhealthy robot would mean that the Robot Manager has received neither hear beat nor shutdown signal from the robot. Things to check would be
Is there is a connectivity issue from Robot to the PEGA platform?
Has the Robot runtime crashed (during an automation)?
For point 2, If the Robot runtime has crashed, you will not be able to re-launch the robot as PEGA recognizes that the robot has already checked-in and rejects the new login. I generally would find the corresponding operator record and delete it from PEGA [Not sure if there is a better way to reset the robot at this time]. This will allow the robot to launch again and PEGA will re-create the robot operator record upon Robot login.
Yes, TarunBolla your suggestion fixed our problem.
As you mentioned in point 2, the robot runtime crashed during an automation. We read a different post suggesting to delete the Operator ID, so we initially deleted the Registration Operator ID (the operator ID we created to handle registering the robot with the robot manager) and then re-created it.
The answer, as you have stated, was to delete the operator ID possessing the same name as the machine running the openspan runtime instance (the operator ID created automatically by the Registration Operator ID when starting the automation).
Also, the pega support team member that helped us mentioned that it would be safe to make sure that any execution flow stemming from an event box within the Openspan automation is set to asynchronous.