Skip to main content

List of events and notifications in PDC

Suggest edit Updated on April 4, 2022

Pega Platform™ sends information about a variety of events, such as alert messages and exceptions, to Pega Predictive Diagnostic Cloud™ (PDC). PDC analyzes and organizes the events to provide diagnostic data and to send notifications about system health.

You can configure the following notification types:

  • Daily digest notifications for business sponsors and program managers
  • Event-based notifications for operations managers and operations staff

To learn to configure notifications in PDC, see Managing notifications in PDC.

To view only the events for which PDC can send notifications, see List of notifications available in PDC.

List of events and event-based notifications

Note: Urgent events require immediate attention. To ensure that your system functions properly, resolve urgent events first.

The following table lists events that PDC recognizes and event-based notifications that PDC can send:

Event detailsUrgent event?PDC notificationCase categorySource of event
PEGA0001: Browser Time
The elapsed time for an HTTP interaction time has exceeded the threshold.
NoNoDatabaseAlert
PEGA0002: DB Commit Time
The elapsed time for a database commit operation has exceeded the threshold.
NoNoDatabaseAlert
PEGA0003: DB Rollback Time
The elapsed time for a database rollback operation has exceeded the threshold.
NoNoDatabaseAlert
PEGA0004: DB Bytes Read
A query to the PegaRULES database has exceeded the threshold for the quantity of data (bytes) that a single interaction can load into memory.
NoNoApplication LogicAlert
PEGA0005: DB Time
The elapsed time for a query to the PegaRULES database has exceeded the operation time threshold.
NoNoDatabaseAlert
PEGA0006: DB Time
The database update operation time has exceeded the threshold.
NoNoNo caseAlert
PEGA0007: DB Time
A database operation has taken longer to complete than the operation time threshold setting.
NoNoNo caseAlert
PEGA0008: PRPC Started
The Pega Platform engine has started successfully.
NoNoNo caseAlert
PEGA0009: PRPC Failed Start
The PegaRULES engine has failed to start.
YesYesOperationsAlert
PEGA0010: Agent Disabled
An agent has been disabled.
YesYes, recommendedOperationsAlert
PEGA0011: Service Total Time
The total time required for parsing data has exceeded the threshold.
NoNoOtherAlert
PEGA0012: Service Mapping Time
The elapsed time required for mapping the data from a response to an outside format has exceeded the threshold setting.
NoNoNo caseAlert
PEGA0013: Service Activity Time
The elapsed time required for running a service activity has exceeded the threshold setting.
NoNoNo caseAlert
PEGA0014: Service Interaction Time
The elapsed time required for mapping the data from a request has exceeded the threshold setting.
NoNoNo caseAlert
PEGA0015: Service Parse Time
The total time required for parsing data has exceeded the threshold.
NoNoNo caseAlert
PEGA0016: Cache Reduced
A cache size has exceeded the target size.
YesYesPega Platform TuningAlert
PEGA0017: Cache Force Reduced
A cache size has exceeded the limit and instances of the cache are being invalidated.
NoYesPega Platform TuningAlert
PEGA0018: PRThreads Limit
The number of PRThreads that were created by a requestor has exceeded the threshold value for the requestor.
NoNoNo caseAlert
PEGA0019: Long Requestor Time
The system master agent has detected that a session has been busy for an excessive amount of time.
NoYes, recommendedOperationsAlert
PEGA0020: Connect Total Time
The total connect interaction time has exceeded the threshold.
NoNoConnectorsAlert
PEGA0021: Declarative Page Memory
The memory used by shared clipboard pages has exceeded the recommended threshold based on a percentage of the JVM total memory.
NoNoNo caseAlert
PEGA0022: Rule Cache Disabled
The rule cache is disabled on a monitored node.
NoYesNo caseAlert
PEGA0023: Rule Cache Enabled
The system-wide rule cache has been enabled.
NoNoNo caseAlert
PEGA0024: Declarative Network Time
The elapsed time to load a declarative network for a specific class has exceeded the threshold.
NoNoPega Platform TuningAlert
PEGA0025: BLOB Access Required
During a list operation, the system has accessed the entire BLOB column because the table that you are querying contains unexposed columns.
NoNoDatabaseAlert
PEGA0026: Acquire DB Connection
The time to acquire either an initial or an existing database connection has exceeded the operation time threshold.
NoNoDatabaseAlert
PEGA0027: DB List Rows
A list operation on the PegaRULES database list has returned more rows than the threshold count limit.
NoYesApplication LogicAlert
PEGA0028: Memory Pool Collection
Garbage Collection (GC) could not reclaim memory from memory pools.
NoYes, recommendedOperationsAlert
PEGA0029: Stream Response Size
The size of an HTML stream that was sent to a browser has exceeded the threshold.
NoNoApplication LogicAlert
PEGA0030: Requestor Limit
The number of active requestors has exceeded the threshold.
NoNoNo caseAlert
PEGA0031: Stream Overwritten
A generated stream has been overwritten without ever being sent to a browser client.
NoNoOtherAlert
PEGA0032: Invalidated Rules
A rule change has produced many invalid entries in the rules assembly cache.
NoNoNo caseAlert
PEGA0033: DB Query Length
Your system has sent an SQL query that was longer than the specified threshold to the PegaRULES database or another SQL database.
NoNoNo caseAlert
PEGA0034: Declare Index
The number of declare indexes from a single interaction has exceeded the threshold.
NoNoApplication LogicAlert
PEGA0035: Clipboard List Size
A Page List property has more elements than the maximum value that is specified in the threshold.
NoNoApplication LogicAlert
PEGA0036: PRPC Shutdown
An administrator has shut down the Pega Platform engine.
NoNoNo caseAlert
PEGA0037: Rule Assembly Time
Rule assembly has taken an unusually long time.
NoNoPega Platform TuningAlert
PEGA0038: Cache Find Synch Time
A requestor's wait time to access the rules assembly cache has exceeded the threshold.
NoNoNo caseAlert
PEGA0039: Blob Size Read
A database query has retrieved a BLOB column (pzPVStream property value, also called the Storage Stream) that is larger than the threshold value.
NoNoApplication LogicAlert
PEGA0040: Blob Size Write
A PegaRULES database write operation has saved a single Storage Stream BLOB (pzPVStream property value) that is larger than the threshold value.
NoNoApplication LogicAlert
PEGA0041: Work Object PR_OTHER
A work object has been saved to the PegaRULES database in a row in the pr_other table, instead of in the standard pc_work table or another table that is identified in a database table data instance.
NoNoOtherAlert
PEGA0042: Package DB Results
The packaging time for a single database query has exceeded the threshold setting.
NoNoApplication LogicAlert
PEGA0043: ADP Queue Wait Time
The queue waiting time for a requestor has exceeded the threshold more than the specified number of times.
NoNoOtherAlert
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.
NoYesOperationsAlert
PEGA0045: ADP Load Wasted
Your application has sent a request to load a page without using the existing one.
NoNoApplication LogicAlert
PEGA0046: ADP Context Setup Wasted
A findPage request was made, but the system canceled the background thread because it did not (or could not) start the loader activity in time to process the request.
NoNoApplication LogicAlert
PEGA0047: ADP Copy Time
The time to copy the context pages from the user thread to the background thread has exceeded the time to run the loader activity.
NoNoApplication LogicAlert
PEGA0048: ADP Context Setup Time
A findPage request has been made but the background thread has already started running the loader activity.
NoNoOtherAlert
PEGA0049: Lucene Search Unavailable
A problem with the Lucene search index has occurred and search results might not be accurate.
NoNoOtherAlert
PEGA0050: Virtual List Copy
A rule or activity has copied a clipboard page list to another list in a way that is inefficient and unnecessary.
NoNoApplication LogicAlert
PEGA0052: DataPage Synchronously Loaded
Wait time exceeded for the page ADP to load asynchronously.
NoNoOtherAlert
PEGA0053: DataPage Load Frequency
A data page has been reloaded more frequently than the configured threshold.
NoNoApplication LogicAlert
PEGA0054: Elasticsearch Time
The elapsed time for a search query against the Elasticsearch index has exceeded the system default threshold.
NoNoDatabaseAlert
PEGA0055: Clock Drift
The clock drift in any of the participating nodes has exceeded the time threshold.
NoYes, recommendedPega Platform TuningAlert
PEGA0056: Defragment PR_SYS_LOCKS
The defragmentation of the table associated with the System-Locks class has exceeded the configured time threshold.
NoNoDecisioningAlert
PEGA0058: DSM IH Read
The Interaction History read time has exceeded its threshold for a customer record or any other entity that is associated with a decision.
NoNoDecisioningAlert
PEGA0059: DSM IH Write
The Interaction History write time has exceeded its threshold for a customer record or any other entity that is associated with a decision.
NoNoDecisioningAlert
PEGA0060: DSM IH Read Row
The number of Interaction History records retrieved for a customer or any other entity that is associated with a decision has exceeded the threshold.
NoNoDecisioningAlert
PEGA0061: DSM IH Write Row
The number of Interaction History records written for a customer or any other entity that is associated with a decision has exceeded the threshold value.
NoNoDecisioningAlert
PEGA0062: DSM Data Flow Time
The total data flow run time has exceeded the threshold.
NoNoDecisioningAlert
PEGA0063: DSM Strategy Time
The time to run a Decision Strategy Manager strategy has exceeded the threshold.
NoNoDecisioningAlert
PEGA0064: DSM Strategy Rows
At least one Decision Strategy Manager strategy shape has processed more rows than the threshold value specifies.
NoNoDecisioningAlert
PEGA0065ADM Response Time
The time for sending a response to the Adaptive Decision Manager (ADM) has exceeded the time threshold.
NoNoDecisioningAlert
PEGA0066: Mobile Data Sync
An offline-enabled mobile app that originates from Pega Platform has failed to synchronize its data after reconnecting to the server.
NoNoOtherAlert
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.
NoYesOperationsAlert
PEGA0068: Social media warning
A social media data set that is the source of a data flow has encountered a non-fatal error that did not stop the data flow.
NoNoOperationsAlert
PEGA0069: Client page load time
The total elapsed time from when the user clicks to when the screen has finished being rendered has exceeded the threshold.
NoNoOtherAlert
PEGA0070: ADM Memory
The Adaptive Decision Manager service has used at least 90% of the allocated memory.
NoYesDecisioningAlert
PEGA0071: VBD Memory
Visual Business Director has used 90% of the allocated memory.
NoYesOperationsAlert
PEGA0072: DSM Data Flow Failed
A Decision Strategy Manager data flow run has failed.
NoYesOperationsAlert
PEGA0073: DSM Data Flow Error
A Decision Strategy Manager data flow has encountered an error.
NoYesOperationsAlert
PEGA0074: DDS Write
The Decision Data Store service write time has exceeded its threshold value for a record.
NoNoDecisioningAlert
PEGA0075: DDS Read
The Decision Data Store service read time has exceeded its threshold.
NoNoDecisioningAlert
PEGA0076: DSM Node Unreachable
At least one node that hosts the Decision Strategy Manager service cannot be reached.
NoYesDecisioningAlert
PEGA0077: DSM DF Assignment
The average time for a data flow assignment has exceeded the threshold.
NoNoDecisioningAlert
PEGA0078: DSM DF Compose Shape
The number of records that a Compose shape returns has exceeded the threshold.
NoNoDecisioningAlert
PEGA0079: DDS Write Size
The size of a record that is written by the Decision Data Store service has exceeded the threshold.
NoNoDecisioningAlert
PEGA0080: DDS Read Size
The size of a record that is read by the Decision Data Store service has exceeded the threshold.
NoNoDecisioningAlert
PEGA0081: VBD Query Time
The time to complete a Visual Business Director query has exceeded the threshold.
NoNoDecisioningAlert
PEGA0082: DSM Data Flow
A Decision Strategy Manager data flow run has started or resumed.
NoYesOperationsAlert
PEGA0083: DSM Data Flow Status
A Decision Strategy Manager data flow run has completed, paused, or stopped.
NoYesOperationsAlert
PEGA0084: Elasticsearch indexing
The number of available index host nodes does not meet the quorum ((replicas/2) + 1) that index writes require to succeed.
NoNoOperationsAlert
PEGA0085: DDS Disk space
Insufficient free disk space for the Decision Data Store.
NoYesOperationsAlert
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.
NoYesOperationsAlert
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.
NoYesOperationsAlert
PEGA0090: Hazelcast Partition
Partition data has been lost from the ungraceful shutdown of a node.
NoYesOperationsAlert
PEGA0098: Job Scheduler Registration
A job scheduler has failed to register for the next run.
YesYes, recommendedOperationsAlert
PEGA0099: Job Scheduler Failure
A job scheduler has failed to complete its run successfully.
YesYes, recommendedOperationsAlert
PEGA0100: Queue processor registration failed
A queue processor has failed to register.
NoYesOperationsAlert
PEGA0101: Queue Processor Stream Node
A queue processor has failed because of a missing or failed stream node.
No

Yes

OperationsAlert
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.
NoYesOperationsAlert
PEGA0103: Queue Processor Run Failed
A queue processor has moved to a failed state and the attempt to recover was unsuccessful.
YesYesOperationsAlert
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.
YesYesOperationsAlert
PEGA0106: Conflicting Queries
Conflicting queries have caused a blockage in the PostgreSQL database system.
NoYes, recommendedOperationsAlert
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.
YesYesOperationsAlert
PEGA0111: Authentication failed
A configured external service could not be reached due to authentication failure.
NoYesOperationsAlert
PEGA0112: Connection time-out
A configured external service could not be reached due to a time-out exception.
NoYesOperationsAlert
PEGA0113: Under-replicated partitions
A cluster contains under-replicated partitions, and Stream service nodes are unreachable.
NoYesOperationsAlert
PEGA0114: Offline partitions count
A cluster contains offline partitions, and Stream service nodes are unreachable.
YesYesOperationsAlert
PEGA0117: QP Long Running Activity
A queue processor activity has run longer than a configured threshold value.
NoNoApplication LogicAlert
PEGA0118: JS Long Running Activity
An activity in a job scheduler has run for a longer time than the configured threshold value.
NoNoApplication LogicAlert
PEGA0119Email listener activity time exceeded the configured threshold
The email listener service activity processing time has exceeded the configured threshold.
NoYesOperationsAlert
PEGA0120Email 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.
NoYesOperationsAlert
PEGA0121Email listener connection issue
An email listener could not connect to the server.
NoYesOperationsAlert
PEGA0125: Service registry heartbeat failed
The service registry failed to update the heartbeat of a node, or it took more than 30 seconds to update the heartbeat.
NoNoStabilityAlert
PEGA0126: Service registry is entering safe mode
A node that could not update its heartbeat stops all cluster-related activity and declares itself unhealthy.
YesNoStabilityAlert
PEGA0127: Service registry recovered from safe mode
The service registry recovered from safe mode by resuming the heartbeat of a node that was previously declared unhealthy.
NoNoStabilityAlert
PEGA0128Email listener authentication issue
A listener has entered the Sleeping or Disabled status due to an authentication failure.
NoYesOperationsAlert
PEGA0129Tracer file disk usage limit reached
Tracer disk usage has reached the configured threshold.
NoYesOperationsAlert
PEGA0131: Slow data flow component
The data flow engine detected that a data flow run has a slow component. The current record takes at least 5 minutes to process.
NoNoStabilityAlert
PEGA0134: Too many items in ready-to-process state
The number of items that are ready to process exceeds the threshold value for the queue processor.
NoNoApplication LogicAlert
PEGA0137: Ready-to-process items not picked by queue processor
Items that are ready to be processed are not picked up by the queue processor within an expected length of time.
NoNoApplication LogicAlert
PEGA0138Simulation run not fully optimized
Strategy associated with a simulation cannot be optimized.
NoNoSimulationsAlert
SECU0001: HTTP Request Corrupted
An HTTP request has received unexpected properties.
NoNoApplication LogicAlert
SECU0002: XML received in post data for web node requestor
Input processing has encountered XML in POST data on Pega Platform web nodes or during the testing of Pega Web Mashup applications.
NoNoNo caseAlert
SECU0003: Rule Not Allowed to run
An unauthorized attempt has been made to run an activity, list view or summary view rule.
NoNoOtherAlert
SECU0004: Stream Not Allowed to run
An attempt to run an HTML stream from the URL has failed in a Pega Platform web node or during the testing of Pega Web Mashup applications.
NoNoOtherAlert
SECU0005Invalid characters in thread name
Pega Platform has encountered a thread name that does not exist in the requestor and whose name contains invalid characters.
NoNoOtherAlert
SECU0006Excessive Login Attempts
An attempt to attack a user session has been blocked.
NoNoOtherAlert
SECU0007Rule could not be executed
An attempt has been made to run a rule that the user is not authorized to run, and the rule security mode is set to WARN or DENY.
NoNoOtherAlert
SECU0008CSRF Detected and Blocked
A cross-site request forgery (CSRF) attack has been detected and blocked.
NoNoNo caseAlert
SECU0009Security Policy Violated
A browser has reported a violation of your application's Content Security Policy.
NoNoOtherAlert
SECU0021: Expired Certificate
An attempt has been made to import an expired certificate into the platform truststore.
NoNoOtherAlert
DBMS0001: (reserved for future use)NoNoNo caseNot applicable
DBMS0002Socket Time-out
A report has failed because a query timed-out in the PostgreSQL database connection.
NoNoOperationsException
DBMS0003Report Time-out
A report has failed because query execution exceeded a time-out in the PostgreSQL report definition.
NoNoOperationsException
DBMS0004Report Join Failure
A report has failed to join due to an unexposed property.
NoNoOperationsException
DBMS0005: Unexposed Property in External Table
A report has failed due to an unexposed property in an external table.
NoNoOperationsException
DBMS0006: Database password exception
The system was unable to open a connection to a database because of an invalid password.
YesYesOperationsException
DBMS0007: Missing Columns in Table
The system has been unable to save a work object because of incorrect mapping in a database.
NoYes, recommendedOperationsException
DBMS0008Unavailable pr_read_stream_function
The pr_read_from_stream function is not available.
NoNoDatabaseException
DBMS0009: Oracle database deadlock
PDC has detected a deadlock in the Oracle database.
YesYesDatabaseException
DBMS0010Idle-in-transaction state for database
A database session is in idle-in-transaction state while executing a query.
NoYesDatabaseException
INTG0001Connect-REST Time-out
A Connect-REST method call has timed out before it received a response.
NoYes, recommendedOperationsException
INTG0002Connect-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, recommendedOperationsException
INTG0003Outbound Mapping Exceptions
The outbound mapping of a connector has failed before Pega Platform created a request.
NoYes, recommendedOperationsException
INTG0004Connect-SOAP Time-out
A Connect-SOAP method call has timed out before it received a response.
NoYes, recommendedOperationsException
OPS0001: (reserved for future use)NoNoNo caseNot applicable
OPS0002: (reserved for future use)NoNoNo caseNot applicable
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, recommendedOperationsException
OPS0004: (reserved for future use)NoNoNo caseNot applicable
OPS0005: Database Recovery Mode
The PostgreSQL database system has entered recovery mode.
YesYesDatabaseException
OPS0006: AL Ticket Failure
PDC has failed to connect to Global Client Support to create an alarm ticket.
NoYesOperationsException
OPS0007DB Connections Unavailable
PostgreSQL has reached the maximum connection capacity and cannot support a new database connection.
YesYesDatabaseException
OPS0008: Tomcat Connection Pool
Pega Platform has generated an Apache Tomcat server connection pool exception.
YesYesOperationsException
OPS0009: Database Configuration
The PostgreSQL database is misconfigured or out of date.
NoNoOperationsException
OPS0010: FTS Not Initialized
Pega Platform has been unable to access or update Elasticsearch.
YesYesOperationsException
OPS0011: Hazelcast instance is not Active
A Hazelcast instance on a monitored node has become inactive and the node generated a corresponding exception.
YesYesOperationsException
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.
NoYesOperationsException
OPS0013Elasticsearch unstable
The Elasticsearch work index has encountered stability problems.
YesYes, recommendedOperationsPDC Insight
OPS0014Search Update Latency
The search index has not been updated recently.
YesYes, recommendedOperationsPDC Insight
OPS0015Agent Status Issue
An agent is not running correctly. The status of the agent has changed to Exception.
NoYes, recommendedOperationsPDC Insight
OPS0016: No space left on device
A node has run out of space during compiling or file writing.
YesYesOperationsException
OPS0017: Queue processor partition state failure
The partition for a queue processor has failed due to an illegal state exception.
YesYesOperationsException
OPS0018: BIX extraction failure
Business Intelligence Exchange extraction has failed.
NoYesOperationsException
OPS0019: (reserved for future use)NoNoNo caseException
OPS0020Database connection state issue
An application has reported issues with database connectivity, which has caused an exception.
NoYesOperationsException
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.
YesYesOperationsException
OPS0022: Unknown Host
An unknown host has caused an exception.
NoYesOperationsException
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.
NoYesOperationsException
OPS0024Java heap out of memory
An application has crashed and generated an Out of memory exception.
YesYesOperationsException
OPS0025Metaspace 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.
YesYesOperationsException
OPS0026S3 Connection pool time-out
The connection pool has timed out on a node.
NoYesOperationsException
OPS0027Agent excessive run duration
An agent has been running for an excessively long time.
NoYes, recommendedOperationsPDC Insight
OPS0028Agent has stale data
The status snapshot of an agent is outdated.
NoYes, recommendedOperationsPDC Insight
OPS0029Correspondence queue latency
An application has significant delays in sending correspondence.
NoYesOperationsPDC Insight
OPS0030Correspondence queue failure
An application has failed to send correspondence.
NoYesOperationsPDC Insight
OPS0031Email processing failure
Inbound email processing has failed with an unsupported operations exception.
NoYesOperationsException
OPS0032Email messaging
Inbound email processing has failed with a javax.mail.* email listener exception.
NoYesOperationsException
OPS0033Email connection timeout
Inbound email processing has failed with a com.sun.mail* email listener exception.
NoYesOperationsException
OPS0034: Listener disabled
A listener is disabled.
NoYesOperationsPDC Insight
OPS0035: Listener errors
A listener has encountered an excessive number of errors.
NoYesOperationsPDC Insight
OPS0036: Listener stopped
An active listener has stopped.
NoYesOperationsPDC Insight
OPS0037Email Listener Request Threshold
The number of pending requests for an email listener has exceeded the configured threshold.
NoYesOperationsPDC Insight
OPS0038: Email Listener TimeThreshold
The average processing time for an email listener has exceeded the configured threshold.
NoYesOperationsPDC Insight
OPS0039: Query Time
A SQL query has run for an excessively long time.
YesYesOperationsPDC Insight
LOCK0001Lock Gone Exception
A user has edited a case that was not locked for editing.
NoNoApplication LogicException
GC0001: Major GC
The JVM has completed major garbage collection.
For more information, see JVM Monitoring.
NoNoOther 
GC0002: Minor GC
The JVM has completed minor garbage collection, which took at least 100 ms.
For more information, see JVM Monitoring.
NoNoOther 
SMTP0001SMTP Connection Error
SMTP could not connect to the host.
NoYesOperationsException
SMTP0002SMTP Connection Reset
The connection was reset while sending an email.
NoYesOperationsException
SMTP0003Email Client Failure
Email cannot be sent, and the email client generated an exception.
NoYesOperationsException
PAL0001Rule I/O time (pxRuleIOElapsed)
Rules were retrieved from the database y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0002DP load time (pxDeclarativePageLoadElapsed)
Data pages were created or loaded y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0003Other I/O time (pxOtherIOElapsed)
Non-rule-resolved instances from the database were accessed y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0004CPU time (pxTotalReqCPU)
Elapsed CPU time accounted for x% of interaction time.
NoNoNo caseAlert
PAL0005DB I/O time (pxRDBIOElapsed)
Database queries were executed y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0006Declarative rules time (pxDeclarativeRulesInvokedElapsed)
Declarative rules were executed y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0007Connector rules time (pxConnectElapsed)
Connect rules were executed y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0008Java generation time (pxJavaAssembleElapsed)
Java was generated y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0009Java compilation time (pxJavaCompileElapsed)
Rules were compiled y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0010Commit time (pxCommitElapsed)
Explicit database commit operations were performed y times, which accounted for x% of interaction time.
NoNoNo caseAlert
PAL0011Inferring Java (pxInferGeneratedJavaHLElapsed)
The engine attempted to avoid rules assembly by identifying existing Java for a rule y times, which accounted for x% of interaction time.
NoNoNo caseAlert
ROBO0001Robot connection lost
A robot has stopped communicating with the Robot Manager server.
NoYesNo caseAlert
ROBO0002Robot failed assignment threshold
The percentage of failed automation tasks for a specific robot has reached the threshold that you configured.
NoYesNo caseAlert
ROBO0003Assignment capacity reached
The number of open assignments for which you assigned robots has reached the configured capacity threshold.
NoYesNo caseAlert
ROBO0004Robot automation time exceeded
A Robot Manager task in a work queue was not completed within a specific period.
NoYesNo caseAlert
ROBO0005Robot automation timed out
An automation task has failed to be completed.
NoYesNo caseAlert
ROBO0006Assignment approaching SLA
By default, this alert appears if a robotic assignment is at 80% of its service-level agreement (SLA) deadline.
NoYesNo caseAlert
ROBO0007Assignment exceeded SLA
An assignment in a work queue is past the SLA deadline.
NoYesNo caseAlert
ROBO0008Scheduling service is down
The agent that handles the scheduling of robots is either turned off or not yet enabled.
NoYesNo caseAlert
ROBO0009RPA service down
The Pega Robotic Process Automation™ (RPA) scheduling service has stopped communicating with Robot Manager server.
NoYesNo caseAlert
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.
NoYesNo caseAlert
ROBO0011: Robot is reaching the Not ready threshold
A robot is about to reach its Not ready threshold.
NoYesNo caseAlert
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.
NoYesNo caseAlert
RS0001: Node health check failure
Node health check has failed for a node type.
NoNoNo caseNot applicable
RS0002: Load Balance Request Failure
A request for load balancing has failed.
NoNoNo caseNot applicable
EXCP0001: Exception
Pega Platform has generated an exception. For more information, open the case in PDC.
NoNew exception
An exception has occurred on a monitored system. Exceptions are unplanned events that interrupt the flow of a running program. A system that operates correctly should not show any exceptions.
ExceptionsException
No event codeNoStale 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.
No caseNot applicable
No event codeNoHealth 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.
No caseNot applicable
No event codeNoNew 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.
No caseNot applicable
No event codeNo

Maintenance mode status
Maintenance window started, ended, or the planned end time changed.

No caseNot applicable
Did you find this content helpful? YesNo

66% found this useful

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