Question
Pegasystems Inc.
US
Last activity: 12 Apr 2017 0:06 EDT
Error After Robot Registration - InternalServerError(500)
We are attemting to register an RPA robot and are getting the a InternalServerError(500) message in the logs. For the Robotics category, we see the following messages;
Regsitering Robot...
Registering Robot step1
Error requesting data from Pega...
Code: InternalServerError(500), Content: System.Threading.Tasks.Task'1[System.String]
(RoboticsService.Start() - Unable to acquire RobotInfo.
The symptom is that the robot registers and display green on the console for about 30 seconds, and then goes red. It stays red even if we shut dow Runtime.
We know the RPA credentials are correct and all other settings in Runtime are correct.
Is there any logging we can enable in Pega to get more information? Is there anything else we can check in the Pega platform that might be causing this?
Accepted Solution
Pegasystems Inc.
US
Hi -
The extensions points for registration, heartbeat, and signoff shipped in Pega 7.2.2 with draft move "ON". The problem is that systems with production level = 5 will not run draft flows. The solution is to specialize the following 3 flows into your application ruleset, turn draft mode off, and save the rules.
- pyRobotRegistration
- pyUpdateHeartbeat
- pySignoffRobot
This will be corrected in Pega 7.3.
Pegasystems Inc.
IN
There are 2 DSS settings as below. I hope the URL for Pega Robotics Studio is valid.
Also, "Registering Robot" message in log is by activity. I couldn't recollect the activity name. Please do a content search for the same string and trace the activity.
There are 2 DSS settings as below. I hope the URL for Pega Robotics Studio is valid.
Also, "Registering Robot" message in log is by activity. I couldn't recollect the activity name. Please do a content search for the same string and trace the activity.
| Pega-ProcessEngine | pegarobotics/HeartbeatInterval | 30 |
| Pega-ProcessEngine | pegarobotics/runtime/DesktopRoboticsURL |
Pegasystems Inc.
US
Thank you for your response. I must have missed it. The actual issue had to do with some of the rules being in draft mode when published at specific levels. As soon as I get the specifics I will post those here.
Accepted Solution
Pegasystems Inc.
US
Hi -
The extensions points for registration, heartbeat, and signoff shipped in Pega 7.2.2 with draft move "ON". The problem is that systems with production level = 5 will not run draft flows. The solution is to specialize the following 3 flows into your application ruleset, turn draft mode off, and save the rules.
- pyRobotRegistration
- pyUpdateHeartbeat
- pySignoffRobot
This will be corrected in Pega 7.3.