Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Resolved issues in Pega Robot Manager

Updated on January 21, 2022

Learn about resolved issues in the Pega Robot Manager application.

Resolved Issues in 8.5.3

Pega Robot Manager continuously improves the user experience and optimizes application performance, including resolving issues, as described below.

Resolved Issues in 8.5.3

Issue ID (internal tracking only)DescriptionSolution
BUG-654301A stale robot operator ruleset was deleted after upgrade.The ProcessStaleRobot agent no longer deletes stale robot operators from the Robots landing page by removing the associated ruleset from the operator record after an upgrade. Instead, the agent stops stale robots and moves them to the Offline status.
BUG-654928The All robot activities window in the Robot drill-in does not list activities that are in progress.The activities that are in progress are available in the All robot activities window for each robot operator.
BUG-654957The work group name cannot exceed 32 characters.The work group name can have up to 64 characters.
BUG-654968Receiving the 200 status code, and the 207 status code, if a robot posts the same assignment twice.If a robot posts the same assignment result twice (for example, due to an issue with runtime configuration), the assignment status now displays the status: 404 - Resource not found.
BUG-654298Standby robots and active robots with enabled schedules are not auto-balanced.For robots running on schedule and in the Otherwise state, Robot Manager moves such robots between work groups as expected if no scheduled action is going to take place in the next 15 minutes.
BUG-654299Robot Manager UI links do not work after clicking Open Robot Manager in an email notification.The URL in the Open Robot Manager email button now addresses the issue.
BUG-654300Robot Manager does not delete the STOP_NOW command, or any other command, when a robot machine crashes. When the machine that hosts a robot crashes, then Robot Manager deletes all pending commands for that robot.
BUG-654347An incorrect icon displays on work group tiles for users with read-only access.For users who have read-only access to the list of work groups in Robot Manager, and applications built on Robot Manager, the icons that indicate the work group settings (for example, that auto-balancing is enabled) display correctly.
BUG-654348Robot Manager deletes a reporting setting when multiple users are simultaneously modifying that setting.When a user updates a reporting setting in one session, but another user has already deleted that setting from the application in a different (simultaneous) session, Robot Manager creates a new version with the updated value.
BUG-654352In the Robot drill-in page, the Last active date-time property value becomes empty when the status of the robot changes while the View all audit window is open.When clicking View all audit for a robot, that robot's status on the Robot drill-in page updates correctly. The Last active property now displays the actual value.
BUG-654520Robot Manager shows an incorrect number of users assigned with a package version in a department unit.Robot Manager now uses the identifier to determine the number of users assigned with a package version in a unit.
BUG-654933A confusing validation message is displayed when a user does not have a work group associated with them in the Work group and requestor mapping decision table.

The validation message was changed to:

Operator <operator_ID> has no work group specified in the work group and requestor mapping table.

BUG-654985The Last active property value for new robots is not blank.The Last active property value in the Robot drill-in screen is empty for new robots, or for robots that never became active.
BUG-655288Assignments in Robot Manager have Unknown automation status if no file attachment was sent.Assignments that did not include a file attachment in the robot response message (for example, error log), but were completed successfully, are correctly classified as Completed in Robot Manager.
BUG-655598The user list cannot exceed 10,000 records, which causes issues with package assignment.User lists can now exceed 10,000 records, without impacting the package assignment flow. In addition, you can now find a specific user record by using autocompletion in search.
BUG-655551Redundant information in the logs in response to a RPA Service registration error.If a user does not have the pyGetAccessGroupForRobotByWorkGroup decision table entry empty, the error message in the logs returns only the necessary information, for example, Robot registration failed: Found an empty access group when registering <robot_name>.
BUG-654296Robot Manager does not count excess robots properly in work groups enabled for auto-balancing.The step to re-calculate the number of excess robots after the auto-balancing engine issues the STOP command to robots in the ready state now provides the correct value.
BUG-657080Cannot view the user list if that list exceeds 10,000 records.You can navigate through a user list when the database contains more than 10,000 records.
BUG-659474Cloud: Cannot download the log file from the Issues landing page when the content storage differs from the Pega database.The content storage implementation was improved to eliminate the issue. You can now download automation issue log files when your content storage is different from the default Pega database.
BUG-650125Robotic work groups display the wrong KPI values because of omitting archived automations from calculations.Work group KPI calculation now includes archived automations.
BUG-660854With more than 10,000 users in an application, the Robot Manager portal is not responding while assigning a Runtime configuration file to a user from the Runtime config drill-in screen.You can now search for users by using a new autocomplete field.
BUG-660866PDC: The CommandStatus REST service causes the PEGA0011 alert.Decreased the REST call duration.
BUG-661937PDC: The Heartbeat REST call causes the PEGA0011 alert.Decreased the REST call duration.
BUG-662184PDC: The Packages REST service causes the PEGA0011 alert.Decreased the REST call duration.
BUG-653406PDC: The Packages_Assignment REST service causes the PEGA0011 alert.Decreased the REST call duration.
BUG-660868PDC: The Register REST service causes the PEGA0011 alert.Decreased the REST call duration.
BUG-660867PDC: The Get RM endpoints REST service causes the PEGA0011 alert.Decreased the REST call duration.
BUG-662629PDC: The pzGetCommandAndSvcOpDetailsForAllRobot activity causes the PEGA0005 alert.The report definition has been improved to accelerate query completion.
BUG-661657PDC: The pzUpdateRobotHeartbeatWrapper activity triggers the PEGA0005 alert.Decreased the activity processing time.
BUG-661427PDC: The pzValidateRoboticOperatorAvailability activity triggers the PEGA0005 alert.Decreased the activity processing time.
BUG-659772PDC: Prolonged database queries by the Auto-balancing engine trigger the PEGA0005 alert.The report definition was improved to accelerate query completion.
BUG-659779PDC: The pyGetNotificationsForOperator query to get notifications takes too long to complete, causing the PEGA0005 alert.The report definition was improved to accelerate query completion.
BUG-659780PDC: The pyGetNotificationsCountForOperator query to get the notification count takes too long, causing the PEGA0005 alert.The report definition was improved to accelerate query completion.
BUG-661409PDC: PEGA0035 alert in the activity pzGetRoboticWorkBasketAssignmentsImproved the report definition to address the root cause of the alert.
BUG-661170PDC: The D_pzGetOperatorsBelongToCurrentApplication activity causes the PEGA0035 alert.The reload strategy of the D_pzGetOperatorsBelongToCurrentApplication activity has been updated.
BUG-654346PDC: The D_pzCaseAssignmentsPastSLA activity is being reloaded frequently, causing the PEGA0035 alert.The reload strategy of D_pzCaseAssignmentsPastSLA has been updated.
BUG-655208PDC: Frequent reloading of the D_pxFetchEntityHierarchy data page causes the PEGA0035 alert.The reload strategy of D_pxFetchEntityHierarchy has been updated.
BUG-663783PDC: EXCP0001 found in the pxTransferAssignment activity when invoked from the pzProcessRoboticAssignments activity.A detailed log message was added for orphan assignments.
BUG-663805PDC: EXCP0001 found in the pzGetRoboticConsolePeopleList activity.The exception was removed.
BUG-664274PDC: The Package drill-in screen causes the SECU0019 alert.The section was updated to receive live updates.
BUG-654303PDC: The Robot drill-in screen causes the SECU0019 alert.The section was updated to receive live updates.
BUG-654551The assignments are not completed properly after the upgrade.The issue was resolved.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us