PEGA0010 alert: Agent processing disabled
The PEGA0010 alert is triggered when agents are manually stopped or terminated and when agents encounter errors during processing.
The alert identifies the agent name, agent activity, queue number (index of this agent
queue from the
Rule-Agent-Queue instance), and the event that triggered
Example message text
Agent "Pega-ProCom" activity "Assign-Corr.SendCorr" disabled due to execution errors
Agent [CustomAgentName:Pega-ProCom] activity [System-Queue-ServiceLevel.ProcessEvent] queue number  terminated manually ErrorMsg: Terminated manually
Reasons for the alert
The system automatically shuts down the agent until a system administrator restarts the agent. Determine the cause of failure by examining the standard Pega log or by accessing the agent management page in the System Management Application to review the "Exception info" column for the disabled agent.Not all agent failures trigger this alert. If an agent run results in an exception, the agent thread goes through a process in which Pega PlatformTM tries to handle the problem in different ways, depending on the exception type.
When the agent is disabled and triggers this alert, the system reschedules the agent automatically to restart at a later time when one of the following situations is true:
- The agent is a system agent, that is, the activity name starts with
Systemand the activity class starts with
Code-, or the agent is a standard agent with Auto Queue management.
The error is tagged as a temporary problem by Pega Platform. For example, when an
OutOfMemoryErrorerror occurs or the agent activity produces the custom Pega Platform exception