We start seen an error in our production environment for RPA runtime running in one of the VM. This error continually throws but couldn’t find the exact reason.
There is no impact to bot functionality and bot is up and running but this error bothers application monitoring.
Note: Some of the sensitive data being masked in exception.
|
2021-09-01 00:00:15,344 [se-nio2-8443-exec-16] [ STANDARD] [ PegaRobotManager:8] (tor.Pega_Robot_Register.Action) ERROR abc.xyz.net| XX.XX.XX.XX|Rest|robotics|v1|register9de4a97425678c5b1288aa70c1669a64|A4SHSHVN3F22V1R4A2WUA6YT00XMSNCRXA - {“error_messages”:[{“robot_id”:“VM79B100220”,“error_message”:“\nRobot registration started…\nRegistering the robot for the first time\nIgnoring the Dynamic System Setting as workgroup from payload is blank\nFetching workgroup from pyGetWorkGroupByRobotID decision table\nFond invalid/empty workgroup from pyGetWorkGroupByRobotID. Fetching workgroup from pyGetWorkGroupForRobotByRequestorOperatorID decision table\nRobot registration failed : Workgroup cannot be null, while registering robot VM79B100220”}]}
2021-09-01 00:00:15,646 [se-nio2-8443-exec-10] [ STANDARD] [ PegaRobotManager:8] (at.Pega_Robot_Heartbeat.Action) ERROR rf02a10273pv00.bnymellon.net|XX.XX.XX.XX|Rest|robotics|v1|heartbeat3a06e053a0726537b202ce4ace81dee7|AZF767VG3ILW0KM3A6BM314WAQVZS5002A - VM79B100220 is not associated with the service operator, BNYMBot VM79B100220.
2021-09-01 00:00:19,987 [OBSCHEDULER_THREAD_4] [ STANDARD] ( internal.access.DatabaseImpl) ERROR - Exception while defragmenting Table::pr_sys_delayed_queue associated with
|
| - |
The pyGetWorkGroupByRobotID in RS: Pega-Robotic-AutomationPackageManagement:08-05-01 and
pyGetWorkGroupForRobotByRequestorOperatorID in RS: Pega-Robotic-AutomationPackageManagement:08-05-01 are not modified due to setting up pegarobotics/WorkgroupSpecifiedInPayloadTakesPrecedence DSS in RS:Pega-Robotic-AutomationPackageManagement to true
Appreciate any valuable inputs and guidance.
