Question
Evonsys
US
Last activity: 23 Mar 2022 15:38 EDT
Runtime Error - nIgnoring the Dynamic System Setting as workgroup from payload is blank
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"}]} |
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.
Accepted Solution
Updated: 1 Oct 2021 15:42 EDT
Evonsys
US
@ThomasSasnett Hi Tom, apologize for late response, the issue is resolved after letting the runtime to create the operator instances gain. This post can be marked as resolved.
Pegasystems Inc.
US
@HemachandraI I believe this is caused by you not specifying a workgroup in your CommonConfig.xml since you have indicated that is where you want it to be pulled from. If you have that DSS set to true, then you must specify the workgroup in the CommonConfig.xml. If that doesn't resolve it, please attach your CommonConfig.xml and I can go from there.
Updated: 23 Mar 2022 16:02 EDT
ACC3
US
@ThomasSasnett Thanks for checking this post. Actually the workgroup already specified in the CommonConfig.xml also available in application. Please find the CommonConfig.xml for more information.
Updated: 23 Mar 2022 16:04 EDT
Evonsys
US
@ThomasSasnettReally appreciate putting your time on investigating this issue. Please find the attachment.
Pegasystems Inc.
US
@HemachandraI As I understand it, with these settings your bot should register with the workgroup in your CommonConfig. One thing you might try is to delete your bot ID and have it re-register to see if it gets the correct workgroup. If not, I would open a support case to get this looked at. If you do open a support case, please post the support number on the post so the resolution can be added.
Evonsys
US
@ThomasSasnett Thanks Tom! We do have a planned production maintenance on next Friday and I’ll try our suggestion and update you back. Once again thanks a lot, and really appreciate for putting your time on checking this issue.
Accepted Solution
Updated: 1 Oct 2021 15:42 EDT
Evonsys
US
@ThomasSasnett Hi Tom, apologize for late response, the issue is resolved after letting the runtime to create the operator instances gain. This post can be marked as resolved.
Pegasystems Inc.
US
Thanks for following and closing the loop here @HemachandraI!
I have marked your reply as the Accepted Solution.