List of events and notifications in PDC
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
The following table lists events that PDC recognizes and event-based notifications that PDC can send:
| Event details | Urgent event? | PDC notification | Case category | Source of event |
|---|---|---|---|---|
| PEGA0001: The elapsed time for an HTTP interaction time has exceeded the threshold. | No | No | Database | Alert |
| PEGA0002: The elapsed time for a database commit operation has exceeded the threshold. | No | No | Database | Alert |
| PEGA0003: The elapsed time for a database rollback operation has exceeded the threshold. | No | No | Database | Alert |
| PEGA0004: A query to the PegaRULES database has exceeded the threshold for the quantity of data (bytes) that a single interaction can load into memory. | No | No | Application Logic | Alert |
| PEGA0005: The elapsed time for a query to the PegaRULES database has exceeded the operation time threshold. | No | No | Database | Alert |
| PEGA0006: The database update operation time has exceeded the threshold. | No | No | No case | Alert |
| PEGA0007: A database operation has taken longer to complete than the operation time threshold setting. | No | No | No case | Alert |
| PEGA0008: The Pega Platform engine has started successfully. | No | No | No case | Alert |
| PEGA0009: The PegaRULES engine has failed to start. | Yes | Yes | Operations | Alert |
| PEGA0010: An agent has been disabled. | Yes | Yes, recommended | Operations | Alert |
| PEGA0011: The total time required for parsing data has exceeded the threshold. | No | No | Other | Alert |
| PEGA0012: The elapsed time required for mapping the data from a response to an outside format has exceeded the threshold setting. | No | No | No case | Alert |
| PEGA0013: The elapsed time required for running a service activity has exceeded the threshold setting. | No | No | No case | Alert |
| PEGA0014: The elapsed time required for mapping the data from a request has exceeded the threshold setting. | No | No | No case | Alert |
| PEGA0015: The total time required for parsing data has exceeded the threshold. | No | No | No case | Alert |
| PEGA0016: Cache Reduced A cache size has exceeded the target size. | Yes | Yes | Pega Platform Tuning | Alert |
| PEGA0017: A cache size has exceeded the limit and instances of the cache are being invalidated. | No | Yes | Pega Platform Tuning | Alert |
| PEGA0018: The number of PRThreads that were created by a requestor has exceeded the threshold value for the requestor. | No | No | No case | Alert |
| PEGA0019: The system master agent has detected that a session has been busy for an excessive amount of time. | No | Yes, recommended | Operations | Alert |
| PEGA0020: The total connect interaction time has exceeded the threshold. | No | No | Connectors | Alert |
| PEGA0021: The memory used by shared clipboard pages has exceeded the recommended threshold based on a percentage of the JVM total memory. | No | No | No case | Alert |
| PEGA0022: The rule cache is disabled on a monitored node. | No | Yes | No case | Alert |
| PEGA0023: The system-wide rule cache has been enabled. | No | No | No case | Alert |
| PEGA0024: The elapsed time to load a declarative network for a specific class has exceeded the threshold. | No | No | Pega Platform Tuning | Alert |
| PEGA0025: During a list operation, the system has accessed the entire BLOB column because the table that you are querying contains unexposed columns. | No | No | Database | Alert |
| PEGA0026: The time to acquire either an initial or an existing database connection has exceeded the operation time threshold. | No | No | Database | Alert |
| PEGA0027: A list operation on the PegaRULES database list has returned more rows than the threshold count limit. | No | Yes | Application Logic | Alert |
| PEGA0028: Garbage Collection (GC) could not reclaim memory from memory pools. | No | Yes, recommended | Operations | Alert |
| PEGA0029: The size of an HTML stream that was sent to a browser has exceeded the threshold. | No | No | Application Logic | Alert |
| PEGA0030: The number of active requestors has exceeded the threshold. | No | No | No case | Alert |
| PEGA0031: A generated stream has been overwritten without ever being sent to a browser client. | No | No | Other | Alert |
| PEGA0032: A rule change has produced many invalid entries in the rules assembly cache. | No | No | No case | Alert |
| PEGA0033: Your system has sent an SQL query that was longer than the specified threshold to the PegaRULES database or another SQL database. | No | No | No case | Alert |
| PEGA0034: The number of declare indexes from a single interaction has exceeded the threshold. | No | No | Application Logic | Alert |
| PEGA0035: A Page List property has more elements than the maximum value that is specified in the threshold. | No | No | Application Logic | Alert |
| PEGA0036: An administrator has shut down the Pega Platform engine. | No | No | No case | Alert |
| PEGA0037: Rule assembly has taken an unusually long time. | No | No | Pega Platform Tuning | Alert |
| PEGA0038: A requestor's wait time to access the rules assembly cache has exceeded the threshold. | No | No | No case | Alert |
| PEGA0039: A database query has retrieved a BLOB column (pzPVStream property value, also called the Storage Stream) that is larger than the threshold value. | No | No | Application Logic | Alert |
| PEGA0040: A PegaRULES database write operation has saved a single Storage Stream BLOB (pzPVStream property value) that is larger than the threshold value. | No | No | Application Logic | Alert |
| PEGA0041: 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. | No | No | Other | Alert |
| PEGA0042: Package DB Results The packaging time for a single database query has exceeded the threshold setting. | No | No | Application Logic | Alert |
| PEGA0043: The queue waiting time for a requestor has exceeded the threshold more than the specified number of times. | No | No | Other | Alert |
| PEGA0044: The maximum number of alert messages with the same ID has been exceeded and further alerts with the same ID are temporarily suppressed. | No | Yes | Operations | Alert |
| PEGA0045: Your application has sent a request to load a page without using the existing one. | No | No | Application Logic | Alert |
| PEGA0046: 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. | No | No | Application Logic | Alert |
| PEGA0047: The time to copy the context pages from the user thread to the background thread has exceeded the time to run the loader activity. | No | No | Application Logic | Alert |
| PEGA0048: A findPage request has been made but the background thread has already started running the loader activity. | No | No | Other | Alert |
| PEGA0049: A problem with the Lucene search index has occurred and search results might not be accurate. | No | No | Other | Alert |
| PEGA0050: A rule or activity has copied a clipboard page list to another list in a way that is inefficient and unnecessary. | No | No | Application Logic | Alert |
| PEGA0052: Wait time exceeded for the page ADP to load asynchronously. | No | No | Other | Alert |
| PEGA0053: A data page has been reloaded more frequently than the configured threshold. | No | No | Application Logic | Alert |
| PEGA0054: The elapsed time for a search query against the Elasticsearch index has exceeded the system default threshold. | No | No | Database | Alert |
| PEGA0055: The clock drift in any of the participating nodes has exceeded the time threshold. | No | Yes, recommended | Pega Platform Tuning | Alert |
| PEGA0056: The defragmentation of the table associated with the System-Locks class has exceeded the configured time threshold. | No | No | Decisioning | Alert |
| PEGA0058: The Interaction History read time has exceeded its threshold for a customer record or any other entity that is associated with a decision. | No | No | Decisioning | Alert |
| PEGA0059: The Interaction History write time has exceeded its threshold for a customer record or any other entity that is associated with a decision. | No | No | Decisioning | Alert |
| PEGA0060: The number of Interaction History records retrieved for a customer or any other entity that is associated with a decision has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0061: 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. | No | No | Decisioning | Alert |
| PEGA0062: The total data flow run time has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0063: The time to run a Decision Strategy Manager strategy has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0064: At least one Decision Strategy Manager strategy shape has processed more rows than the threshold value specifies. | No | No | Decisioning | Alert |
| PEGA0065: The time for sending a response to the Adaptive Decision Manager (ADM) has exceeded the time threshold. | No | No | Decisioning | Alert |
| PEGA0066: An offline-enabled mobile app that originates from Pega Platform has failed to synchronize its data after reconnecting to the server. | No | No | Other | Alert |
| PEGA0067: A social media data set that is the source of a data flow has encountered a fatal error that stopped the data flow. | No | Yes | Operations | Alert |
| PEGA0068: 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. | No | No | Operations | Alert |
| PEGA0069: The total elapsed time from when the user clicks to when the screen has finished being rendered has exceeded the threshold. | No | No | Other | Alert |
| PEGA0070: The Adaptive Decision Manager service has used at least 90% of the allocated memory. | No | Yes | Decisioning | Alert |
| PEGA0071: Visual Business Director has used 90% of the allocated memory. | No | Yes | Operations | Alert |
| PEGA0072: A Decision Strategy Manager data flow run has failed. | No | Yes | Operations | Alert |
| PEGA0073: A Decision Strategy Manager data flow has encountered an error. | No | Yes | Operations | Alert |
| PEGA0074: The Decision Data Store service write time has exceeded its threshold value for a record. | No | No | Decisioning | Alert |
| PEGA0075: The Decision Data Store service read time has exceeded its threshold. | No | No | Decisioning | Alert |
| PEGA0076: At least one node that hosts the Decision Strategy Manager service cannot be reached. | No | Yes | Decisioning | Alert |
| PEGA0077: The average time for a data flow assignment has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0078: The number of records that a Compose shape returns has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0079: The size of a record that is written by the Decision Data Store service has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0080: The size of a record that is read by the Decision Data Store service has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0081: VBD Query Time The time to complete a Visual Business Director query has exceeded the threshold. | No | No | Decisioning | Alert |
| PEGA0082: A Decision Strategy Manager data flow run has started or resumed. | No | Yes | Operations | Alert |
| PEGA0083: A Decision Strategy Manager data flow run has completed, paused, or stopped. | No | Yes | Operations | Alert |
| PEGA0084: The number of available index host nodes does not meet the quorum ((replicas/2) + 1) that index writes require to succeed. | No | No | Operations | Alert |
| PEGA0085: Insufficient free disk space for the Decision Data Store. | No | Yes | Operations | Alert |
| PEGA0086: 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. | No | Yes | Operations | Alert |
| PEGA0087: The performance of a service does not comply with the service-level agreement (SLA), and a fallback activity is in use. | No | Yes | Operations | Alert |
| PEGA0090: Partition data has been lost from the ungraceful shutdown of a node. | No | Yes | Operations | Alert |
| PEGA0098: Job Scheduler Registration A job scheduler has failed to register for the next run. | Yes | Yes, recommended | Operations | Alert |
| PEGA0099: Job Scheduler Failure A job scheduler has failed to complete its run successfully. | Yes | Yes, recommended | Operations | Alert |
| PEGA0100: A queue processor has failed to register. | No | Yes | Operations | Alert |
| PEGA0101: A queue processor has failed because of a missing or failed stream node. | No | Yes | Operations | Alert |
| PEGA0102: A queue processor has failed to pull the delayed items from the database and push these items to the Stream Service. | No | Yes | Operations | Alert |
| PEGA0103: A queue processor has moved to a failed state and the attempt to recover was unsuccessful. | Yes | Yes | Operations | Alert |
| PEGA0104: Background tasks have exceeded a threshold time during an attempt to acquire a thread from an agent’s thread pool executor. | Yes | Yes | Operations | Alert |
| PEGA0106: Conflicting queries have caused a blockage in the PostgreSQL database system. | No | Yes, recommended | Operations | Alert |
| PEGA0108: 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. | Yes | Yes | Operations | Alert |
| PEGA0111: A configured external service could not be reached due to authentication failure. | No | Yes | Operations | Alert |
| PEGA0112: A configured external service could not be reached due to a time-out exception. | No | Yes | Operations | Alert |
| PEGA0113: A cluster contains under-replicated partitions, and Stream service nodes are unreachable. | No | Yes | Operations | Alert |
| PEGA0114: A cluster contains offline partitions, and Stream service nodes are unreachable. | Yes | Yes | Operations | Alert |
| PEGA0117: A queue processor activity has run longer than a configured threshold value. | No | No | Application Logic | Alert |
| PEGA0118: An activity in a job scheduler has run for a longer time than the configured threshold value. | No | No | Application Logic | Alert |
| PEGA0119: The email listener service activity processing time has exceeded the configured threshold. | No | Yes | Operations | Alert |
| PEGA0120: 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. | No | Yes | Operations | Alert |
| PEGA0121: An email listener could not connect to the server. | No | Yes | Operations | Alert |
| PEGA0125: The service registry failed to update the heartbeat of a node, or it took more than 30 seconds to update the heartbeat. | No | No | Stability | Alert |
| PEGA0126: A node that could not update its heartbeat stops all cluster-related activity and declares itself unhealthy. | Yes | No | Stability | Alert |
| PEGA0127: The service registry recovered from safe mode by resuming the heartbeat of a node that was previously declared unhealthy. | No | No | Stability | Alert |
| PEGA0128: A listener has entered the Sleeping or Disabled status due to an authentication failure. | No | Yes | Operations | Alert |
| PEGA0129: Tracer disk usage has reached the configured threshold. | No | Yes | Operations | Alert |
| PEGA0131: The data flow engine detected that a data flow run has a slow component. The current record takes at least 5 minutes to process. | No | No | Stability | Alert |
| PEGA0134: The number of items that are ready to process exceeds the threshold value for the queue processor. | No | No | Application Logic | Alert |
| PEGA0137: Items that are ready to be processed are not picked up by the queue processor within an expected length of time. | No | No | Application Logic | Alert |
| PEGA0138: Simulation run not fully optimized Strategy associated with a simulation cannot be optimized. | No | No | Simulations | Alert |
| SECU0001: An HTTP request has received unexpected properties. | No | No | Application Logic | Alert |
| SECU0002: Input processing has encountered XML in POST data on Pega Platform web nodes or during the testing of Pega Web Mashup applications. | No | No | No case | Alert |
| SECU0003: An unauthorized attempt has been made to run an activity, list view or summary view rule. | No | No | Other | Alert |
| SECU0004: 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. | No | No | Other | Alert |
| SECU0005: Pega Platform has encountered a thread name that does not exist in the requestor and whose name contains invalid characters. | No | No | Other | Alert |
| SECU0006: An attempt to attack a user session has been blocked. | No | No | Other | Alert |
| SECU0007: 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. | No | No | Other | Alert |
| SECU0008: A cross-site request forgery (CSRF) attack has been detected and blocked. | No | No | No case | Alert |
| SECU0009: A browser has reported a violation of your application's Content Security Policy. | No | No | Other | Alert |
| SECU0021: Expired Certificate An attempt has been made to import an expired certificate into the platform truststore. | No | No | Other | Alert |
| DBMS0001: (reserved for future use) | No | No | No case | Not applicable |
| DBMS0002: A report has failed because a query timed-out in the PostgreSQL database connection. | No | No | Operations | Exception |
| DBMS0003: A report has failed because query execution exceeded a time-out in the PostgreSQL report definition. | No | No | Operations | Exception |
| DBMS0004: A report has failed to join due to an unexposed property. | No | No | Operations | Exception |
| DBMS0005: A report has failed due to an unexposed property in an external table. | No | No | Operations | Exception |
| DBMS0006: The system was unable to open a connection to a database because of an invalid password. | Yes | Yes | Operations | Exception |
| DBMS0007: The system has been unable to save a work object because of incorrect mapping in a database. | No | Yes, recommended | Operations | Exception |
| DBMS0008: The pr_read_from_stream function is not available. | No | No | Database | Exception |
| DBMS0009: PDC has detected a deadlock in the Oracle database. | Yes | Yes | Database | Exception |
| DBMS0010: A database session is in idle-in-transaction state while executing a query. | No | Yes | Database | Exception |
| INTG0001: A Connect-REST method call has timed out before it received a response. | No | Yes, recommended | Operations | Exception |
| INTG0002: A Connect-FTP method call has failed to copy a file from one file system to another file system by using FTP. | No | Yes, recommended | Operations | Exception |
| INTG0003: The outbound mapping of a connector has failed before Pega Platform created a request. | No | Yes, recommended | Operations | Exception |
| INTG0004: A Connect-SOAP method call has timed out before it received a response. | No | Yes, recommended | Operations | Exception |
| OPS0001: (reserved for future use) | No | No | No case | Not applicable |
| OPS0002: (reserved for future use) | No | No | No case | Not applicable |
| OPS0003: A service was unable to process a service request for a pool or package because of a requestor pool lock. | No | Yes, recommended | Operations | Exception |
| OPS0004: (reserved for future use) | No | No | No case | Not applicable |
| OPS0005: The PostgreSQL database system has entered recovery mode. | Yes | Yes | Database | Exception |
| OPS0006: PDC has failed to connect to Global Client Support to create an alarm ticket. | No | Yes | Operations | Exception |
| OPS0007: PostgreSQL has reached the maximum connection capacity and cannot support a new database connection. | Yes | Yes | Database | Exception |
| OPS0008: Pega Platform has generated an Apache Tomcat server connection pool exception. | Yes | Yes | Operations | Exception |
| OPS0009: The PostgreSQL database is misconfigured or out of date. | No | No | Operations | Exception |
| OPS0010: Pega Platform has been unable to access or update Elasticsearch. | Yes | Yes | Operations | Exception |
| OPS0011: A Hazelcast instance on a monitored node has become inactive and the node generated a corresponding exception. | Yes | Yes | Operations | Exception |
| OPS0012: An application has deliberately triggered a stack trace in an activity. A stack trace typically indicates a serious issue in the application. | No | Yes | Operations | Exception |
| OPS0013: The Elasticsearch work index has encountered stability problems. | Yes | Yes, recommended | Operations | PDC Insight |
| OPS0014: The search index has not been updated recently. | Yes | Yes, recommended | Operations | PDC Insight |
| OPS0015: An agent is not running correctly. The status of the agent has changed to Exception. | No | Yes, recommended | Operations | PDC Insight |
| OPS0016: A node has run out of space during compiling or file writing. | Yes | Yes | Operations | Exception |
| OPS0017: The partition for a queue processor has failed due to an illegal state exception. | Yes | Yes | Operations | Exception |
| OPS0018: Business Intelligence Exchange extraction has failed. | No | Yes | Operations | Exception |
| OPS0019: (reserved for future use) | No | No | No case | Exception |
| OPS0020: An application has reported issues with database connectivity, which has caused an exception. | No | Yes | Operations | Exception |
| OPS0021: A Kafka broker could not be started while a node tried to replace another node during an update or upgrade. | Yes | Yes | Operations | Exception |
| OPS0022: An unknown host has caused an exception. | No | Yes | Operations | Exception |
| OPS0023: 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. | No | Yes | Operations | Exception |
| OPS0024: An application has crashed and generated an Out of memory exception. | Yes | Yes | Operations | Exception |
| OPS0025: 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. | Yes | Yes | Operations | Exception |
| OPS0026: The connection pool has timed out on a node. | No | Yes | Operations | Exception |
| OPS0027: An agent has been running for an excessively long time. | No | Yes, recommended | Operations | PDC Insight |
| OPS0028: The status snapshot of an agent is outdated. | No | Yes, recommended | Operations | PDC Insight |
| OPS0029: An application has significant delays in sending correspondence. | No | Yes | Operations | PDC Insight |
| OPS0030: An application has failed to send correspondence. | No | Yes | Operations | PDC Insight |
| OPS0031: Inbound email processing has failed with an unsupported operations exception. | No | Yes | Operations | Exception |
| OPS0032: Inbound email processing has failed with a javax.mail.* email listener exception. | No | Yes | Operations | Exception |
| OPS0033: Inbound email processing has failed with a com.sun.mail* email listener exception. | No | Yes | Operations | Exception |
| OPS0034: A listener is disabled. | No | Yes | Operations | PDC Insight |
| OPS0035: A listener has encountered an excessive number of errors. | No | Yes | Operations | PDC Insight |
| OPS0036: L An active listener has stopped. | No | Yes | Operations | PDC Insight |
| OPS0037: The number of pending requests for an email listener has exceeded the configured threshold. | No | Yes | Operations | PDC Insight |
| OPS0038: The average processing time for an email listener has exceeded the configured threshold. | No | Yes | Operations | PDC Insight |
| OPS0039: A SQL query has run for an excessively long time. | Yes | Yes | Operations | PDC Insight |
| LOCK0001: A user has edited a case that was not locked for editing. | No | No | Application Logic | Exception |
| GC0001: The JVM has completed major garbage collection. For more information, see JVM Monitoring. | No | No | Other | |
| GC0002: The JVM has completed minor garbage collection, which took at least 100 ms. For more information, see JVM Monitoring. | No | No | Other | |
| SMTP0001: SMTP could not connect to the host. | No | Yes | Operations | Exception |
| SMTP0002: The connection was reset while sending an email. | No | Yes | Operations | Exception |
| SMTP0003: Email cannot be sent, and the email client generated an exception. | No | Yes | Operations | Exception |
| PAL0001: (pxRuleIOElapsed) Rules were retrieved from the database y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0002: (pxDeclarativePageLoadElapsed) Data pages were created or loaded y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0003: (pxOtherIOElapsed) Non-rule-resolved instances from the database were accessed y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0004: (pxTotalReqCPU) Elapsed CPU time accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0005: (pxRDBIOElapsed) Database queries were executed y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0006: (pxDeclarativeRulesInvokedElapsed) Declarative rules were executed y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0007: (pxConnectElapsed) Connect rules were executed y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0008: (pxJavaAssembleElapsed) Java was generated y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0009: (pxJavaCompileElapsed) Rules were compiled y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0010: (pxCommitElapsed) Explicit database commit operations were performed y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| PAL0011: (pxInferGeneratedJavaHLElapsed) The engine attempted to avoid rules assembly by identifying existing Java for a rule y times, which accounted for x% of interaction time. | No | No | No case | Alert |
| ROBO0001: A robot has stopped communicating with the Robot Manager server. | No | Yes | No case | Alert |
| ROBO0002: The percentage of failed automation tasks for a specific robot has reached the threshold that you configured. | No | Yes | No case | Alert |
| ROBO0003: The number of open assignments for which you assigned robots has reached the configured capacity threshold. | No | Yes | No case | Alert |
| ROBO0004: A Robot Manager task in a work queue was not completed within a specific period. | No | Yes | No case | Alert |
| ROBO0005: An automation task has failed to be completed. | No | Yes | No case | Alert |
| ROBO0006: By default, this alert appears if a robotic assignment is at 80% of its service-level agreement (SLA) deadline. | No | Yes | No case | Alert |
| ROBO0007: An assignment in a work queue is past the SLA deadline. | No | Yes | No case | Alert |
| ROBO0008: The agent that handles the scheduling of robots is either turned off or not yet enabled. | No | Yes | No case | Alert |
| ROBO0009: The Pega Robotic Process Automation™ (RPA) scheduling service has stopped communicating with Robot Manager server. | No | Yes | No case | Alert |
| 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. | No | Yes | No case | Alert |
| ROBO0011: Robot is reaching the Not ready threshold A robot is about to reach its Not ready threshold. | No | Yes | No case | Alert |
| 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. | No | Yes | No case | Alert |
| RS0001: Node health check has failed for a node type. | No | No | No case | Not applicable |
| RS0002: A request for load balancing has failed. | No | No | No case | Not applicable |
| EXCP0001: Pega Platform has generated an exception. For more information, open the case in PDC. | No | New 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. | Exceptions | Exception |
| No event code | No | 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. | No case | Not applicable |
| No event code | No | 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. | No case | Not applicable |
| No event code | No | 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. | No case | Not applicable |
| No event code | No | Maintenance mode status | No case | Not applicable |
Previous topic Advanced PDC facilities Next topic List of notifications available in Pega Predictive Diagnostic Cloud