Table of Contents

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 you with diagnostic data, and to send notifications informing the recipients about system health.

You can configure the following notification types:

To learn how to configure your notifications, see Managing notifications in Pega Predictive Diagnostic Cloud.

Daily digest notifications

As part of system governance, subscribers receive the following scheduled types of digests to keep them up to date about the status of a monitored system:

  • Improvement Plan: Details
    A complete Improvement Plan for the selected system, with cases divided into categories. For more information, see Pega Predictive Diagnostic Cloud Improvement Plan overview. As part of PDC onboarding, subscribe to this daily digest.
  • New items daily
    A list of all new issues that have occurred within the 24-hour period before sending the digest.
  • TOP 5 reliability
    A report on up to the five most urgent issues that affect your system's reliability, in the form of a summary of the effect of the issues on the system, displayed as the amount of time spent resolving requests. The digest shows a comparison of the time spent in the previous week as a percentage. As part of your PDC onboarding, subscribe to this daily digest.
  • TOP 5 user impact
    A report on up to the five most urgent issues that affect user experience, in the form of a summary of the effect on the system, displayed as the amount of time spent resolving requests. The digest shows a comparison of the time spent in the previous week as a percentage. As part of your PDC onboarding, subscribe to this daily digest.
  • Event summary
    A summary of events that recently occurred on the selected systems.
  • Cases summary
    A summary of the cases that PDC created for the selected systems. The report contains the total number of cases and the number of cases that PDC created in the last 24 hours.

Event-based notifications

Subscribers can receive notifications whenever the relevant events occur. Critical events require urgent attention. To ensure the correct and efficient functioning of your system, you should resolve critical events first.

As part of your PDC onboarding, to receive notifications for the most important events, subscribe to the notifications that are marked as recommended in the following list of events and event-based notifications. After using PDC for some time, you can revise these subscriptions to ensure that you stay informed about the events that are most relevant to your system and application.

List of events and event-based notifications

The following table lists all events that PDC recognizes, as well as event-based notifications that PDC can send to the selected recipients:

Event details Critical event? PDC notification Case category Source of event
PEGA0001Browser Time
The elapsed time for an HTTP interaction time has exceeded the threshold.
No No Database Alert
PEGA0002: DB Commit Time
The elapsed time for a database commit operation has exceeded the threshold.
No No Database Alert
PEGA0003: DB Rollback Time
The elapsed time for a database rollback operation has exceeded the threshold.
No No Database Alert
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.
No No Application Logic Alert
PEGA0005: DB Time
The elapsed time for a query to the PegaRULES database has exceeded the operation time threshold.
No No Database Alert
PEGA0006DB Time
The database update operation time has exceeded the threshold.
No No No case Alert
PEGA0007DB Time
A database operation has taken longer to complete than the operation time threshold setting.
No No No case Alert
PEGA0008PRPC Started
The Pega Platform engine has started successfully.
No No No case Alert
PEGA0009PRPC Failed Start
The PegaRULES engine has failed to start.
Yes Yes Operations Alert
PEGA0010Agent Disabled
An agent has been disabled.
Yes Yes, recommended Operations Alert
PEGA0011Service Total Time
The total time required for parsing data has exceeded the threshold.
No No Other Alert
PEGA0012Service Mapping Time
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
PEGA0013Service Activity Time
The elapsed time required for running a service activity has exceeded the threshold setting.
No No No case Alert
PEGA0014Service Interaction Time
The elapsed time required for mapping the data from a request has exceeded the threshold setting.
No No No case Alert
PEGA0015Service Parse Time
The total time required for parsing data has exceeded the threshold.
No No No case Alert
PEGA0016Cache Reduced
A cache size has exceeded the target size.
Yes Yes Pega Platform Tuning Alert
PEGA0017Cache Force Reduced
A cache size has exceeded the limit and instances of the cache are being invalidated.
No Yes Pega Platform Tuning Alert
PEGA0018PRThreads Limit
The number of PRThreads that were created by a requestor has exceeded the threshold value for the requestor.
No No No case Alert
PEGA0019Long Requestor Time
The system master agent has detected that a session has been busy for an excessive amount of time.
No Yes, recommended Operations Alert
PEGA0020Connect Total Time
The total connect interaction time has exceeded the threshold.
No No Connectors Alert
PEGA0021Declarative Page Memory
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
PEGA0022Rule Cache Disabled
The rule cache is disabled on a monitored node.
No Yes No case Alert
PEGA0023Rule Cache Enabled
The system-wide rule cache has been enabled.
No No No case Alert
PEGA0024Declarative Network Time
The elapsed time to load a declarative network for a specific class has exceeded the threshold.
No No Pega Platform Tuning Alert
PEGA0025BLOB Access Required
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
PEGA0026Acquire DB Connection
The time to acquire either an initial or an existing database connection has exceeded the operation time threshold.
No No Database Alert
PEGA0027DB List Rows
A list operation on the PegaRULES database list has returned more rows than the threshold count limit.
No Yes Application Logic Alert
PEGA0028Memory Pool Collection
Garbage Collection (GC) could not reclaim memory from memory pools.
No Yes, recommended Operations Alert
PEGA0029Stream Response Size
The size of an HTML stream that was sent to a browser has exceeded the threshold.
No No Application Logic Alert
PEGA0030Requestor Limit
The number of active requestors has exceeded the threshold.
No No No case Alert
PEGA0031Stream Overwritten
A generated stream has been overwritten without ever being sent to a browser client.
No No Other Alert
PEGA0032Invalidated Rules
A rule change has produced many invalid entries in the rules assembly cache.
No No No case Alert
PEGA0033DB Query Length
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
PEGA0034Declare Index
The number of declare indexes from a single interaction has exceeded the threshold.
No No Application Logic Alert
PEGA0035Clipboard List Size
A Page List property has more elements than the maximum value that is specified in the threshold.
No No Application Logic Alert
PEGA0036PRPC Shutdown
An administrator has shut down the Pega Platform engine.
No No No case Alert
PEGA0037Rule Assembly Time
Rule assembly has taken an unusually long time.
No No Pega Platform Tuning Alert
PEGA0038Cache Find Synch Time
A requestor's wait time to access the rules assembly cache has exceeded the threshold.
No No No case Alert
PEGA0039Blob 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.
No No Application Logic Alert
PEGA0040Blob Size Write
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
PEGA0041Work 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.
No No Other Alert
PEGA0042Package DB Results
The packaging time for a single database query has exceeded the threshold setting.
No No Application Logic Alert
PEGA0043ADP Queue Wait Time
The queue waiting time for a requestor has exceeded the threshold more than the specified number of times.
No No Other Alert
PEGA0044Throttle Alerts
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
PEGA0045ADP Load Wasted
Your application has sent a request to load a page without using the existing one.
No No Application Logic Alert
PEGA0046ADP 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.
No No Application Logic Alert
PEGA0047ADP 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.
No No Application Logic Alert
PEGA0048ADP Context Setup Time
A findPage request has been made but the background thread has already started running the loader activity.
No No Other Alert
PEGA0049Lucene Search Unavailable
A problem with the Lucene search index has occurred and search results might not be accurate.
No No Other Alert
PEGA0050Virtual List Copy
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
PEGA0052DataPage Synchronously Loaded
Wait time exceeded for the page ADP to load asynchronously.
No No Other Alert
PEGA0053DataPage Load Frequency
A data page has been reloaded more frequently than the configured threshold.
No No Application Logic Alert
PEGA0054Elasticsearch Time
The elapsed time for a search query against the Elasticsearch index has exceeded the system default threshold.
No No Database Alert
PEGA0055Clock Drift
The clock drift in any of the participating nodes has exceeded the time threshold.
No Yes, recommended Pega Platform Tuning Alert
PEGA0056Defragment PR_SYS_LOCKS
The defragmentation of the table associated with the System-Locks class has exceeded the configured time threshold.
No No Decisioning Alert
PEGA0058DSM 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.
No No Decisioning Alert
PEGA0059DSM 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.
No No Decisioning Alert
PEGA0060DSM 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.
No No Decisioning Alert
PEGA0061DSM 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.
No No Decisioning Alert
PEGA0062DSM Data Flow Time
The total data flow run time has exceeded the threshold.
No No Decisioning Alert
PEGA0063DSM Strategy Time
The time to run a Decision Strategy Manager strategy has exceeded the threshold.
No No Decisioning Alert
PEGA0064DSM Strategy Rows
At least one Decision Strategy Manager strategy shape has processed more rows than the threshold value specifies.
No No Decisioning Alert
PEGA0065ADM Response Time
The time for sending a response to the Adaptive Decision Manager (ADM) has exceeded the time threshold.
No No Decisioning Alert
PEGA0066Mobile Data Sync
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
PEGA0067Social 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.
No Yes Operations Alert
PEGA0068Social 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.
No No Operations Alert
PEGA0069Client page load time
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
PEGA0070ADM Memory
The Adaptive Decision Manager service has used at least 90% of the allocated memory.
No Yes Decisioning Alert
PEGA0071VBD Memory
Visual Business Director has used 90% of the allocated memory.
No Yes Operations Alert
PEGA0072DSM Data Flow Failed
A Decision Strategy Manager data flow run has failed.
No Yes Operations Alert
PEGA0073DSM Data Flow Error
A Decision Strategy Manager data flow has encountered an error.
No Yes Operations Alert
PEGA0074DDS Write
The Decision Data Store service write time has exceeded its threshold value for a record.
No No Decisioning Alert
PEGA0075DDS Read
The Decision Data Store service read time has exceeded its threshold.
No No Decisioning Alert
PEGA0076DSM Node Unreachable
At least one node that hosts the Decision Strategy Manager service cannot be reached.
No Yes Decisioning Alert
PEGA0077DSM DF Assignment
The average time for a data flow assignment has exceeded the threshold.
No No Decisioning Alert
PEGA0078DSM DF Compose Shape
The number of records that a Compose shape returns has exceeded the threshold.
No No Decisioning Alert
PEGA0079DDS Write Size
The size of a record that is written by the Decision Data Store service has exceeded the threshold.
No No Decisioning Alert
PEGA0080DDS Read Size
The size of a record that is read by the Decision Data Store service has exceeded the threshold.
No No Decisioning Alert
PEGA0081VBD Query Time
The time to complete a Visual Business Director query has exceeded the threshold.
No No Decisioning Alert
PEGA0082DSM Data Flow
A Decision Strategy Manager data flow run has started or resumed.
No Yes Operations Alert
PEGA0083DSM Data Flow Status
A Decision Strategy Manager data flow run has completed, paused, or stopped.
No Yes Operations Alert
PEGA0084Elasticsearch indexing
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
PEGA0085DDS Disk space
Insufficient free disk space for the Decision Data Store.
No Yes Operations Alert
PEGA0086Requestor 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.
No Yes Operations Alert
PEGA0087Service SLA Violation
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
PEGA0090Hazelcast Partition
Partition data has been lost from the ungraceful shutdown of a node.
No Yes Operations Alert
PEGA0098Job Scheduler Registration
A job scheduler has failed to register for the next run.
Yes Yes, recommended Operations Alert
PEGA0099Job Scheduler Failure
A job scheduler has failed to complete its run successfully.
Yes Yes, recommended Operations Alert
PEGA0100Queue processor registration failed
A queue processor has failed to register.
No Yes Operations Alert
PEGA0101Queue Processor Stream Node
A queue processor has failed because of a missing or failed stream node.
No

Yes

Operations Alert
PEGA0102Queue Processor Schedule
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
PEGA0103Queue Processor Run Failed
A queue processor has moved to a failed state and the attempt to recover was unsuccessful.
Yes Yes Operations Alert
PEGA0104Insufficient Thread Pool Size
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
PEGA0106Conflicting Queries
Conflicting queries have caused a blockage in the PostgreSQL database system.
No Yes, recommended Operations Alert
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.
Yes Yes Operations Alert
PEGA0111: Authentication failed
A configured external service could not be reached due to authentication failure.
No Yes Operations Alert
PEGA0112: Connection time-out
A configured external service could not be reached due to a time-out exception.
No Yes Operations Alert
PEGA0113: Under-replicated partitions
A cluster contains under-replicated partitions, and Stream service nodes are unreachable.
No Yes Operations Alert
PEGA0114: Offline partitions count
A cluster contains offline partitions, and Stream service nodes are unreachable.
Yes Yes Operations Alert
PEGA0117QP Long Running Activity
A queue processor activity has run longer than a configured threshold value.
No No Application Logic Alert
PEGA0118JS Long Running Activity
An activity in a job scheduler has run for a longer time than the configured threshold value.
No No Application Logic Alert
SECU0001HTTP Request Corrupted
An HTTP request has received unexpected properties.
No No Application Logic Alert
SECU0002XML 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.
No No No case Alert
SECU0003Rule Not Allowed to run
An unauthorized attempt has been made to run an activity, list view or summary view rule.
No No Other Alert
SECU0004Stream 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.
No No Other Alert
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.
No No Other Alert
SECU0006Excessive Login Attempts
An attempt to attack a user session has been blocked.
No No Other Alert
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.
No No Other Alert
SECU0008CSRF Detected and Blocked
A cross-site request forgery (CSRF) attack has been detected and blocked.
No No No case Alert
SECU0009Security Policy Violated
A browser has reported a violation of your application's Content Security Policy.
No No Other Alert
DBMS0001: (reserved for future use) No No No case Not applicable
DBMS0002Socket Time-out
A report has failed because a query timed-out in the PostgreSQL database connection.
No No Operations Exception
DBMS0003Report Time-out
A report has failed because query execution exceeded a time-out in the PostgreSQL report definition.
No No Operations Exception
DBMS0004: Report Join Failure
A report has failed because of unexposed properties.
No No Operations Exception
DBMS0005: Unoptimized property
A report has failed to join due to an unoptimized property.
No No Operations Exception
DBMS0006: Database password exception
The system was unable to open a connection to a database because of an invalid password.
Yes Yes Operations Exception
DBMS0007: Missing Columns in Table
The system has been unable to save a work object because of incorrect mapping in a database.
No Yes, recommended Operations Exception
DBMS0008: Unavailable pr_read_stream_function
The pr_read_from_stream function is not available.
No No Database Exception
DBMS0009: Oracle database deadlock
PDC has detected a deadlock in the Oracle database.
Yes Yes Database Exception
INTG0001Connect-REST Time-out
A Connect-REST method call has timed out before it received a response.
No Yes, recommended Operations Exception
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.
No Yes, recommended Operations Exception
INTG0003Outbound Mapping Exceptions
The outbound mapping of a connector has failed before Pega Platform created a request.
No Yes, recommended Operations Exception
INTG0004Connect-SOAP Time-out
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: Requestor Pool Locked
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: Database Recovery Mode
The PostgreSQL database system has entered recovery mode.
Yes Yes Database Exception
OPS0006: AL Ticket Failure
PDC has failed to connect to Global Client Support to create an alarm ticket.
No Yes Operations Exception
OPS0007: DB Connections Unavailable
PostgreSQL has reached the maximum connection capacity and cannot support a new database connection.
Yes Yes Database Exception
OPS0008: Tomcat Connection Pool
Pega Platform has generated an Apache Tomcat server connection pool exception.
Yes Yes Operations Exception
OPS0009: Database Configuration
The PostgreSQL database is misconfigured or out of date.
No No Operations Exception
OPS0010: FTS Not Initialized
Pega Platform has been unable to access or update Elasticsearch.
Yes Yes Operations Exception
OPS0011: Hazelcast instance is not Active
A Hazelcast instance on a monitored node has become inactive and the node generated a corresponding exception.
Yes Yes Operations Exception
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.
No Yes Operations Exception
OPS0013Elasticsearch unstable
The Elasticsearch work index has encountered stability problems.
Yes Yes, recommended Operations PDC Insight
OPS0014Search Update Latency
The search index has not been updated recently.
Yes Yes, recommended Operations PDC Insight
OPS0015Agent Status Issue
An agent is not running correctly. The status of the agent has changed to Exception.
No Yes, recommended Operations PDC Insight
OPS0016: No space left on device
A node has run out of space during compiling or file writing.
Yes Yes Operations Exception
OPS0017: Queue processor partition state failure
The partition for a queue processor has failed due to an illegal state exception.
Yes Yes Operations Exception
OPS0018: BIX extraction failure
Business Intelligence Exchange extraction has failed.
No Yes Operations Exception
OPS0019: (reserved for future use) No No No case Exception
OPS0020: Database connection state issue
An application has reported issues with database connectivity, which has caused an exception.
No Yes Operations Exception
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.
Yes Yes Operations Exception
OPS0022: Unknown Host
An unknown host has caused an exception.
No Yes Operations Exception
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.
No Yes Operations Exception
OPS0024: Java heap out of memory
An application has crashed and generated an Out of memory exception.
Yes Yes Operations Exception
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.
Yes Yes Operations Exception
OPS0026: S3 Connection pool time-out
The connection pool has timed out on a node.
No Yes Operations Exception
OPS0027Agent excessive run duration
An agent has been running for an excessively long time.
No Yes, recommended Operations PDC Insight
OPS0028Agent has stale data
The status snapshot of an agent is outdated.
No Yes, recommended Operations PDC Insight
OPS0029Correspondence queue latency
An application has significant delays in sending correspondence.
No Yes Operations PDC Insight
OPS0030Correspondence queue failure
An application has failed to send correspondence.
No Yes Operations PDC Insight
OPS0031Email processing failure
Inbound email processing has failed with an unsupported operations exception.
No Yes Operations Exception
OPS0032Email messaging
Inbound email processing has failed with a javax.mail.* email listener exception.
No Yes Operations Exception
OPS0033Email connection timeout
Inbound email processing has failed with a com.sun.mail* email listener exception.
No Yes Operations Exception
OPS0034Listener disabled
An email listener has become disabled.
No Yes Operations PDC Insight
OPS0035Listener errors
An email listener has encountered an excessive number of errors.
No Yes Operations PDC Insight
OPS0036Listener stopped
An active email listener has stopped.
No Yes Operations PDC Insight
OPS0037Listener Request Threshold
The number of pending requests for a listener has exceeded the configured threshold.
No Yes Operations PDC Insight
OPS0038Listener TimeThreshold
The average processing time for a listener has exceeded the configured threshold.
No Yes Operations PDC Insight
OPS0039: Query Time
A SQL query has run for an excessively long time.
Yes Yes Operations PDC Insight
LOCK0001Lock Gone Exception
A user has edited a case that was not locked for editing.
No No Application Logic Exception
GC0001: Major GC
The JVM has completed major garbage collection.
No No Other  
GC0002: Minor GC
The JVM has completed minor garbage collection, which took at least 100 ms.
No No Other  
SMTP0001SMTP Connection Error
SMTP could not connect to the host.
No Yes Operations Exception
SMTP0002SMTP Connection Reset
The connection was reset while sending an email.
No Yes Operations Exception
SMTP0003Email Client Failure
Email cannot be sent, and the email client generated an exception. PDC generates the SMTP0003 event in the following situations:
  • Authentication credentials supplied for the SMTP server are incorrect or have expired.
  • Cannot connect to the email client. The host has sent the 421 response code, which implies that your message was temporarily deferred by the recipient server.
  • Cannot send email. The SMTP server responded with the 451 code and message sending failed.
  • Cannot send email. The SMTP server responded with the 454 code (Temporary service failure).
No Yes Operations Exception
PAL0001Rule I/O time (pxRuleIOElapsed)
Rules were retrieved from the database y times, which accounted for x% of interaction time.
No No No case Alert
PAL0002DP load time (pxDeclarativePageLoadElapsed)
Data pages were created or loaded y times, which accounted for x% of interaction time.
No No No case Alert
PAL0003Other I/O time (pxOtherIOElapsed)
Non-rule-resolved instances from the database were accessed y times, which accounted for x% of interaction time.
No No No case Alert
PAL0004CPU time (pxTotalReqCPU)
Elapsed CPU time accounted for x% of interaction time.
No No No case Alert
PAL0005DB I/O time (pxRDBIOElapsed)
Database queries were executed y times, which accounted for x% of interaction time.
No No No case Alert
PAL0006Declarative rules time (pxDeclarativeRulesInvokedElapsed)
Declarative rules were executed y times, which accounted for x% of interaction time.
No No No case Alert
PAL0007Connector rules time (pxConnectElapsed)
Connect rules were executed y times, which accounted for x% of interaction time.
No No No case Alert
PAL0008Java generation time (pxJavaAssembleElapsed)
Java was generated y times, which accounted for x% of interaction time.
No No No case Alert
PAL0009Java compilation time (pxJavaCompileElapsed)
Rules were compiled y times, which accounted for x% of interaction time.
No No No case Alert
PAL0010Commit time (pxCommitElapsed)
Explicit database commit operations were performed y times, which accounted for x% of interaction time.
No No No case Alert
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.
No No No case Alert
ROBO0001Robot connection lost
A robot has stopped communicating with the Robot Manager server.
No Yes No case Alert
ROBO0002Robot failed assignment threshold
The percentage of failed automation tasks for a specific robot has reached the threshold that you configured.
No Yes No case Alert
ROBO0003Assignment capacity reached
The number of open assignments for which you assigned robots has reached the configured capacity threshold.
No Yes No case Alert
ROBO0004Robot automation time exceeded
A Robot Manager task in a work queue was not completed within a specific period.
No Yes No case Alert
ROBO0005Robot automation timed out
An automation task has failed to be completed.
No Yes No case Alert
ROBO0006Assignment approaching SLA
By default, this alert appears if a robotic assignment is at 80% of its service-level agreement (SLA) deadline.
No Yes No case Alert
ROBO0007Assignment exceeded SLA
An assignment in a work queue is past the SLA deadline.
No Yes No case Alert
ROBO0008Scheduling service is down
The agent that handles the scheduling of robots is either turned off or not yet enabled.
No Yes No case Alert
ROBO0009RPA service down
The Pega Robotic Process Automation™ (RPA) scheduling service has stopped communicating with Robot Manager server.
No Yes No case Alert
EXCP0001: Exception
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 Pulse down
This notification is specific to node status. Every two minutes, PDC receives a message with the node health status. If PDC does not receive this message, it means that the system pulse is down.
No case Not applicable
No event code No Health status change
The health status of a system on the Enterprise landing page has changed. One or more critical events have been recently received to change server health to Critical, or the server has failed to send a health status message.
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, this notification is sent only when a case has more than 10 associated events.
No case Not applicable
No event code No SLA Reporting: failed requests
The number of requests that have failed within the set time window has exceeded the threshold.
You can configure the threshold by clicking the Properties icon in the header of PDC, and then selecting Notifications > SLA Notifications.
No case Not applicable
No event code No SLA Reporting: requests past SLA
The number of requests that have not met the SLA within the set time window has exceeded the threshold.
No case Not applicable
Suggest Edit

Related Content

Have a question? Get answers now.

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