Skip to main content

List of notifications available in Pega Predictive Diagnostic Cloud

Suggest edit Updated on April 4, 2022

Pega Predictive Diagnostic Cloud (PDC) sends notifications for events that are important and require immediate attention or additional action. Each notification informs you about an issue in your system, such as unresponsive components, exceeded time thresholds, or low resources.

The following table lists all events for which PDC can send event-based notifications:

Event detailsUrgent event?Recommended?
PEGA0009: PRPC Failed Start
The PegaRULES engine has failed to start.
YesNo
PEGA0010: Agent Disabled
An agent has been disabled.
YesYes
PEGA0016: Cache Reduced
A cache size has exceeded the target size.
YesNo
PEGA0017: Cache Force Reduced
A cache size has exceeded the limit and instances of the cache are being invalidated.
NoNo
PEGA0019: Long Requestor Time
The system master agent has detected that a session has been busy for an excessive amount of time.
NoYes
PEGA0022: Rule Cache Disabled
The rule cache is disabled on a monitored node.
NoNo
PEGA0027: DB List Rows
A list operation on the PegaRULES database list has returned more rows than the threshold count limit.
NoNo
PEGA0028: Memory Pool Collection
Garbage Collection (GC) could not reclaim memory from memory pools.
NoYes
PEGA0044: Throttle Alerts
The maximum number of alert messages with the same ID has been exceeded and further alerts with the same ID are temporarily suppressed.
NoNo
PEGA0055: Clock Drift
The clock drift in any of the participating nodes has exceeded the time threshold.
NoYes
PEGA0067: Social media error
A social media data set that is the source of a data flow has encountered a fatal error that stopped the data flow.
NoNo
PEGA0070: ADM Memory
The Adaptive Decision Manager service has used at least 90% of the allocated memory.
NoNo
PEGA0071: VBD Memory
Visual Business Director has used 90% of the allocated memory.
NoNo
PEGA0072: DSM Data Flow Failed
A Decision Strategy Manager data flow run has failed.
NoNo
PEGA0073: DSM Data Flow Error
A Decision Strategy Manager data flow has encountered an error.
NoNo
PEGA0076: DSM Node Unreachable
At least one node that hosts the Decision Strategy Manager service cannot be reached.
NoNo
PEGA0082: DSM Data Flow
A Decision Strategy Manager data flow run has started or resumed.
NoNo
PEGA0083: DSM Data Flow Status
A Decision Strategy Manager data flow run has completed, paused, or stopped.
NoNo
PEGA0085: DDS Disk space
Insufficient free disk space for the Decision Data Store.
NoNo
PEGA0086: Requestor Lock
The monitored system is not processing a browser request because the session (requestor) has been locked for an excessive amount of time while processing prior requests.
NoNo
PEGA0087: Service SLA Violation
The performance of a service does not comply with the service-level agreement (SLA), and a fallback activity is in use.
NoNo
PEGA0090: Hazelcast Partition
Partition data has been lost from the ungraceful shutdown of a node.
NoNo
PEGA0098: Job Scheduler Registration
A job scheduler has failed to register for the next run.
YesYes
PEGA0099: Job Scheduler Failure
A job scheduler has failed to complete its run successfully.
YesYes
PEGA0100: Queue processor registration failed
A queue processor has failed to register.
NoNo
PEGA0101: Queue Processor Stream Node
A queue processor has failed because of a missing or failed stream node.
No

No

PEGA0102: Queue Processor Schedule
A queue processor has failed to pull the delayed items from the database and push these items to the Stream Service.
NoNo
PEGA0103: Queue Processor Run Failed
A queue processor has moved to a failed state and the attempt to recover was unsuccessful.
YesNo
PEGA0104: Insufficient Thread Pool Size
Background tasks have exceeded a threshold time during an attempt to acquire a thread from an agent’s thread pool executor.
YesNo
PEGA0106: Conflicting Queries
Conflicting queries have caused a blockage in the PostgreSQL database system.
NoYes
PEGA0108: Split-brain issue
Split-brain is a state of decomposition in which a single cluster of nodes separates into multiple clusters of nodes, each operating as if the other no longer exists. Cluster fracturing is the process by which nodes end up in a split-brain state. For more information, see Split-Brain Syndrome and cluster fracturing FAQs.
YesNo
PEGA0111: Authentication failed
A configured external service could not be reached due to authentication failure.
NoNo
PEGA0112: Connection time-out
A configured external service could not be reached due to a time-out exception.
NoNo
PEGA0113: Under-replicated partitions
A cluster contains under-replicated partitions, and Stream service nodes are unreachable.
NoNo
PEGA0114: Offline partitions count
A cluster contains offline partitions, and Stream service nodes are unreachable.
YesNo
PEGA0119: Email listener activity time exceeded the configured threshold
The email listener service activity processing time has exceeded the configured threshold.
NoNo
PEGA0120: Email listener time-out issue
An email listener has timed out while sending email through the host. This alert relates to the sender configuration whenever any read or write time out occurs.
NoNo
PEGA0121: Email listener connection issue
An email listener could not connect to the server.
NoNo
PEGA0128: Email listener authentication issue
A listener has entered the Sleeping or Disabled status due to an authentication failure.
NoNo
PEGA0129: Tracer file disk usage limit reached
Tracer disk usage has reached the configured threshold.
NoNo
DBMS0006: Database password exception
The system was unable to open a connection to a database because of an invalid password.
YesNo
DBMS0007: Missing Columns in Table
The system has been unable to save a work object because of incorrect mapping in a database.
NoYes
DBMS0009: Oracle database deadlock
PDC has detected a deadlock in the Oracle database.
YesNo
DBMS0010: Idle-in-transaction state for database
A database session is in idle-in-transaction state while executing a query.
NoNo
INTG0001: Connect-REST Time-out
A Connect-REST method call has timed out before it received a response.
NoYes
INTG0002: Connect-FTP Failure
A Connect-FTP method call has failed to copy a file from one file system to another file system by using FTP.
NoYes
INTG0003: Outbound Mapping Exceptions
The outbound mapping of a connector has failed before Pega Platform created a request.
NoYes
INTG0004: Connect-SOAP Time-out
A Connect-SOAP method call has timed out before it received a response.
NoYes
OPS0003: Requestor Pool Locked
A service was unable to process a service request for a pool or package because of a requestor pool lock.
NoYes
OPS0005: Database Recovery Mode
The PostgreSQL database system has entered recovery mode.
YesNo
OPS0006: AL Ticket Failure
PDC has failed to connect to Global Client Support to create an alarm ticket.
NoNo
OPS0007: DB Connections Unavailable
PostgreSQL has reached the maximum connection capacity and cannot support a new database connection.
YesNo
OPS0008: Tomcat Connection Pool
Pega Platform has generated an Apache Tomcat server connection pool exception.
YesNo
OPS0010: FTS Not Initialized
Pega Platform has been unable to access or update Elasticsearch.
YesNo
OPS0011: Hazelcast instance is not Active
A Hazelcast instance on a monitored node has become inactive and the node generated a corresponding exception.
YesNo
OPS0012: Application stack trace
An application has deliberately triggered a stack trace in an activity. A stack trace typically indicates a serious issue in the application.
NoNo
OPS0013: Elasticsearch unstable
The Elasticsearch work index has encountered stability problems.
YesYes
OPS0014: Search Update Latency
The search index has not been updated recently.
YesYes
OPS0015: Agent Status Issue
An agent is not running correctly. The status of the agent has changed to Exception.
NoYes
OPS0016: No space left on device
A node has run out of space during compiling or file writing.
YesNo
OPS0017: Queue processor partition state failure
The partition for a queue processor has failed due to an illegal state exception.
YesNo
OPS0018: BIX extraction failure
Business Intelligence Exchange extraction has failed.
NoNo
OPS0020: Database connection state issue
An application has reported issues with database connectivity, which has caused an exception.
NoNo
OPS0021: Cannot start Kafka broker
A Kafka broker could not be started while a node tried to replace another node during an update or upgrade.
YesNo
OPS0022: Unknown Host
An unknown host has caused an exception.
NoNo
OPS0023: Service package time-out
An application has been unable to process a service interaction because a node has reached the configured concurrent execution threshold as defined in the service package. For more information about service packages, see About Service Package data instances.
NoNo
OPS0024: Java heap out of memory
An application has crashed and generated an Out of memory exception.
YesNo
OPS0025: Metaspace is out of memory
An application has generated the java.lang.OutOfMemoryError exception. This exception indicates that an object could not be allocated in Metaspace because Metaspace has run out of memory.
YesNo
OPS0026: S3 Connection pool time-out
The connection pool has timed out on a node.
NoNo
OPS0027: Agent excessive run duration
An agent has been running for an excessively long time.
NoYes
OPS0028: Agent has stale data
The status snapshot of an agent is outdated.
NoYes
OPS0029: Correspondence queue latency
An application has significant delays in sending correspondence.
NoNo
OPS0030: Correspondence queue failure
An application has failed to send correspondence.
NoNo
OPS0031: Email processing failure
Inbound email processing has failed with an unsupported operations exception.
NoNo
OPS0032: Email messaging
Inbound email processing has failed with a javax.mail.* email listener exception.
NoNo
OPS0033: Email connection timeout
Inbound email processing has failed with a com.sun.mail* email listener exception.
NoNo
OPS0034: Listener disabled
A listener is disabled.
NoNo
OPS0035: Listener errors
A listener has encountered an excessive number of errors.
NoNo
OPS0036: Listener stopped
An active listener has stopped.
NoNo
OPS0037: Email listener Request Threshold
The number of pending requests for an email listener has exceeded the configured threshold.
NoNo
OPS0038: Email Listener TimeThreshold
The average processing time for an email listener has exceeded the configured threshold.
NoNo
OPS0039: Query Time
A SQL query has run for an excessively long time.
YesNo
SMTP0001: SMTP Connection Error
SMTP could not connect to the host.
NoNo
SMTP0002: SMTP Connection Reset
The connection was reset while sending an email.
NoNo
SMTP0003: Email Client Failure
Email cannot be sent, and the email client generated an exception.
NoNo
ROBO0001: Robot connection lost
A robot has stopped communicating with the Robot Manager server.
NoNo
ROBO0002: Robot failed assignment threshold
The percentage of failed automation tasks for a specific robot has reached the threshold that you configured.
NoNo
ROBO0003: Assignment capacity reached
The number of open assignments for which you assigned robots has reached the configured capacity threshold.
NoNo
ROBO0004: Robot automation time exceeded
A Robot Manager task in a work queue was not completed within a specific period.
NoNo
ROBO0005: Robot automation timed out
An automation task has failed to be completed.
NoNo
ROBO0006: Assignment approaching SLA
By default, this alert appears if a robotic assignment is at 80% of its service-level agreement (SLA) deadline.
NoNo
ROBO0007: Assignment exceeded SLA
An assignment in a work queue is past the SLA deadline.
NoNo
ROBO0008: Scheduling service is down
The agent that handles the scheduling of robots is either turned off or not yet enabled.
NoNo
ROBO0009: RPA service down
The Pega Robotic Process Automation™ (RPA) scheduling service has stopped communicating with Robot Manager server.
NoNo
ROBO0010: Robot is reaching the consecutive failed assignments threshold defined on its work group
A robot reached the threshold defined for consecutive failures as defined for its work group.
NoNo
ROBO0011: Robot is reaching the Not ready threshold
A robot is about to reach its Not ready threshold.
NoNo
ROBO0012: An error occurred during an attempt to automatically archive/purge the Pega Robot Runtime data that caused the job to fail
An auto-purge or auto-archive operation has failed.
NoNo

Pulse down (Stale pulse)
The system pulse agent on the legacy system pulse node has not completed housekeeping tasks for more than five minutes. By default, the system pulse agents completes a housekeeping task every minute on every node. A stale pulse might indicate that an agent is unresponsive or that a data discrepancy occurred on a monitored node. A stale pulse has no direct impact on Pega Infinity, but can indicate that your system is unstable. As a best practice, restart the node that reports a stale pulse.

NoNo
Health status change
The health status of a system on the Enterprise landing page has changed. For example, PDC recently received one or more critical events, or PDC has not received a health status message from the node for ten minutes and did not receive a shut-down report from the node. Check whether the node is responsive and whether it can connect to PDC. If you are still unable to diagnose the problem, take a thread dump to investigate the management daemon thread, and then restart the node.
NoNo
New alert action item
The system has created a new case for a performance or operations issue. To ensure that you receive messages only about significant issues, PDC sends this notification only when a case has more than 10 associated events.
NoNo
Maintenance mode status
Maintenance window started, ended, or the planned end time changed.
No

No

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us