Summary

Log file errors occur after upgrading from Robot Manager (RM) v5.1 to RM v6.1. However, errors continue to occur in Pega logs after the application version is changed from 02.02.01 from 02.01.01. The advanced agents (uncategorized) are introduced in the Pega-Robotic-AutomationPackageManagement ruleset in the 02.02.01 version. The agent access group refers to the highest application. However, the ruleset stack in the logs displays the reference for 02.01.01 version and the errors occur. The errors occur in the log when the newly added agents in Robot Manager v6.1 are started. 

Error Messages

internal.async.AgentQueue) ERROR - Agent Pega-Robotic-AutomationPackageManagement #4: Data-Admin-Operator-ID.pzProcessRobotScheduleActions encountered an execution error. Restarting after delay.
pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'PZPROCESSROBOTSCHEDULEACTIONS' that applies to 'Data-Admin-Operator-ID'. There were 2 rules with this name in the rulebase, but none matched this request. The 2 rules named 'PZPROCESSROBOTSCHEDULEACTIONS' defined in the rulebase are:
2 related to applies-to class 'Data-Admin-Operator-ID', but were defined in rulesets which are not in your rulesetlist: {Pega-Robotic-AutomationPackageManagement, Pega-Robotic-AutomationPackageManagement}.

0000007e SystemOut 857 [PegaWorkManager :11][STANDARD][][eManagement](ernal.async.BatchRequestorTask)ERROR - Batch activity "Data Robot.pzMonitorRobotCommandAndHeartbeat" threw:
pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'PZMONITORROBOTCOMMANDANDHEARTBEAT' that applies to 'Data-Robot'. There were 1 rules with this name in the rulebase, but none matched this request. The 1 rules named 'PZMONITORROBOTCOMMANDANDHEARTBEAT' defined in the rulebase are:
1 related to applies-to class 'Data-Robot', but were defined in rulesets which are not in your rulesetlist: 'Pega-Robotic-AutomationPackageManagement.

SystemOut858[PegaWorkManager:11][STANDARD][][eManagement](internal.async.AgentQueue)ERROR - Agent Pega-Robotic-AutomationPackageManagement #3:Data-Robot.pzMonitorRobotCommandAndHeartbeat encountered an execution error.Restarting after delay.
pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'PZMONITORROBOTCOMMANDANDHEARTBEAT' that applies to 'Data-Robot'. There were 1 rules with this name in the rulebase, but none matched this request. The 1 rules named 'PZMONITORROBOTCOMMANDANDHEARTBEAT' defined in the rulebase are: 1 related to applies-to class 'Data-Robot', but were defined in rulesets which are not in your rulesetlist: 'Pega-Robotic-AutomationPackageManagement.

Steps to Reproduce

Unknown

Root Cause

Resolution

1. Delete the Pega-Robotic-AutomationPackageManagement agent schedule and wait for 10 minutes or restart the server 
2. Open the recreated Pega-Robotic-AutomationPackageManagement agent schedule and confirm if the access group on the Security tab is correct (PegaRoboticConsole:Administrators) if the error messages in the logs still display
3. Update the access group by changing it's application from AutomationPackageManagement:02.01.01 to PegaRoboticAutomationConsole:02.02.01 if for some reason it is still AutomationPackageManagement:Administrators