Close popover

Table of Contents

PEGA0010 alert: Agent processing disabled

Version:

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 the alert.

Example message text

Agent "Pega-ProCom" activity "Assign-Corr.SendCorr" disabled due to execution errors

or

Agent [CustomAgentName:Pega-ProCom] activity [System-Queue-ServiceLevel.ProcessEvent] queue number [1] 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 SMA agent management page 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 the Pega Platform 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 System and 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 the Pega Platform. For example, when an OutOfMemoryError error occurs or the agent activity produces the custom Pega Platform exception PRInterruptedException

Suggest Edit

Have a question? Get answers now.

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