Cases in Pega Predictive Diagnostic Cloud

Pega Predictive Diagnostic Cloud™ (PDC) creates cases that represent problems in your system. Find out more about a particular case type to learn about the root cause of a problem, and to identify ways to resolve the problem and prevent it from occurring again.

Cases are divided into categories that represent the areas of your system where a problem occurs. The following list contains the categories in the order in which they appear in the Improvement Plan:

Database

Cases in this category represent problems that occur in your database configuration.

Case type Description
Acquire DB Connection The time to acquire either an initial or an existing database connection has exceeded the operation time threshold.
DB Commit Time The elapsed time for a database commit operation has exceeded the threshold.
DB Connections Unavailable PostgreSQL has reached the maximum connection capacity and cannot support a new database connection.
DB Rollback Time The elapsed time for a database rollback operation has exceeded the threshold.
DB Time The elapsed time for a query to the PegaRULES database has exceeded the operation time threshold.
Elasticsearch Time The elapsed time for a search query against the Elasticsearch index has exceeded the system default threshold.
Database Recovery Mode The PostgreSQL database system has entered recovery mode.
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.

Pega Platform Tuning

Cases in this category represent problems with your Pega Platform™ configuration.

Case type Description
Cache Force Reduced A cache size has exceeded the limit and instances of the cache are being invalidated.
Clock Drift The clock drift in any of the participating nodes has exceeded the time threshold.
Declarative Network Time The elapsed time to load a declarative network for a specific class has exceeded the threshold.
Rule Assembly Time Rule assembly has taken an unusually long time.

Connectors

Cases in this category represent problems with the connectors in your application.

Case type Description
Connect Total Time The total connect interaction time has exceeded the threshold.

Decisioning

Cases in this category represent problems in Decision Strategy Manager (DSM).

Case type Description
ADM Response Time

The total time for sending the response to the Adaptive Decision Manager (ADM) has exceeded the time threshold.

DSM Data Flow Time The total time for running a data flow in single or batch mode has exceeded the threshold.
DSM DF Assignment The average time for a data flow assignment has exceeded the threshold.
DSM DF Compose Shape The number of records that a Compose shape returns has exceeded the threshold.
DSM Node Unreachable The status of a Decision Strategy Manager service node has changed from normal to unreachable.
DDS Read Size The size of the record that is read by the Decision Data Store service has exceeded the threshold.
DDS Read The Decision Data Store (DDS) service interaction time has exceeded the threshold.
DDS Write Size The size of the record that is written by the Decision Data Store service has exceeded the threshold.
DDS Write The Decision Data Store service write time has exceeded its threshold for a record.
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.
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.
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.
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.
DSM Strategy Rows At least one Decision Strategy Manager strategy shape has processed more rows than the threshold value specifies.
DSM Strategy Time The time to run a Decision Strategy Manager strategy has exceeded the threshold.
VBD Query Time The time to complete a Visual Business Director query has exceeded the threshold.

Exceptions

Cases in this category represent errors in the code.

Case type Description
Exception Pega Platform has generated an exception.

Operations

Cases in this category represent problems related to the run-time operation of your application.

Case type Description
Agent Disabled An agent has been stopped.
Agent Status Issue

This case type can represent one of the following problems:

  • An agent is in the exception state.
  • An agent has run for an excessively long period.
  • An agent has an outdated snapshot.
AL Ticket Failure PDC could not connect with Global Customer Service to submit a ticket.
Application stack trace An application has requested a stack trace.
BIX failure BIX extraction of data has failed.
Conflicting Queries Conflicting queries were detected in the PostgreSQL database system.
Connect-FTP Failure A Connect-FTP method call has failed while trying to copy a file.
Connect-REST Timeout A Connect-REST method call has timed out before receiving a response.
Connect-SOAP Timeout A Connect-SOAP method call has timed out before receiving a response.
Database Configuration The PostgreSQL database system has encountered configuration errors.
Database password exception The system was unable to open a connection to a database because of an invalid password.
DSM Data Flow Error A data flow has encountered an error.
DSM Data Flow Failed A data flow run has failed.
DDS Disk space Decision Data Store disk free space below threshold.
Elasticsearch Broken The Elasticsearch work index has encountered stability problems.
Elasticsearch indexing The number of available index host nodes does not meet the quorum ((replicas/2) + 1) that index writes require to succeed.
FTS Not Initialized Elasticsearch full text search features have not initialized correctly and could not be accessed or updated.
Hazelcast instance is not Active Exceptions on a node have indicated that the instance of Hazelcast is inactive.
Insufficient Thread Pool Size Slow allocation of resources has caused delays in processing.
Job Scheduler Failure A job scheduler has failed to complete its run successfully.
Job Scheduler Registration A job scheduler has failed to register for the next run.
Long Requestor Time A long-running requestor has been detected.
Memory Pool Collection Garbage Collection (GC) could not reclaim memory from memory pools.
Missing Columns in Table The system has been unable to save a work object due to schema changes. Columns are missing in a table.
No space left on device

A node has run out of space in one of the following circumstances:

  • During compilation
  • While writing files
Outbound Mapping Exceptions A connector has failed while mapping data on the outbound message.
PRPC Failed Start The PegaRULES engine has failed to start.
Queue processor partition state failure A queue processor partition has failed due to an illegal state exception.
Queue Processor Run Failed A queue processor has failed to complete its run successfully.
Queue Processor Stream Node A queue processor has failed because a stream node is not available in the cluster.
Report Join Failure A report has failed because of unexposed properties.
Report Time-out A report has failed because query execution exceeded a time-out in the PostgreSQL report definition.
Requestor Pool Locked A service was unable to process a service request for a pool or package because of a requestor pool lock.
Requestor Lock Requestor has been locked by a busy thread.
Serious Search Update Latency PDC has detected significant latency in the search index updates.
Service SLA Violation Service SLA violation has been detected.
Socket Time-out A report has failed because a query timed-out in the PostgreSQL database connection.
SMTP Connection Error SMTP could not connect to the host.
SMTP Connection Reset The connection has been reset while sending an email.
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.
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.
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.
Tomcat Connection Pool Tomcat Database Connection Manager has been unable to allocate a session to serve a request.
Unoptimized property A report has failed to join due to an unoptimized property.
VBD Memory Visual Business Director has used 90% of the allocated memory.

Application Logic

Cases in this category represent issues in the way that your application is built.

Case type Description
Clipboard List Size A Page List property has more elements than the maximum value that is specified in the threshold.
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.
DB List Rows A list operation on the PegaRULES database list has returned more rows than the threshold count limit.
Declare Index The number of declare indexes from a single interaction has exceeded the threshold.
Stream Response Size The size of an HTML stream that was sent to a browser has exceeded the threshold.
Lock Gone Exception The lock on a case or object has been released before the case or object was updated.
HTTP Request Corrupted An HTTP request has received unexpected properties.

Other

The following cases represent problems that currently do not belong to any category:

Case type Description
ADP Queue Wait Time The queue waiting time for a requestor has exceeded the threshold more than the specified number of times.
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.
ADP Context Setup Time A findPage request has been made but the background thread has already started running the loader activity.
Browser Time The elapsed time for an HTTP interaction time has exceeded the threshold.
Client page load time The total elapsed time from when the user clicks to when the screen finishes being rendered has exceeded the threshold.
Mobile Data Sync An offline-enabled mobile app that originates from Pega Platform has failed to synchronize its data after reconnecting to the server.
Lucene Search Unavailable A problem with the Lucene search index has occurred and search results might not be accurate.
Excessive Login Attempts An attempt to attack a user session has been blocked.
Rule Not Allowed to run An unauthorized attempt has been made to run an activity, list view or summary view rule.
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.
Security Policy Violated A browser has reported a violation of your application's Content Security Policy.
Rule 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.
Invalid characters in thread name Pega Platform has encountered a thread name that does not exist in the requestor and whose name contains invalid characters.
Service Total Time The total request time required for a service request has exceeded the threshold.
Stream Overwritten A generated stream has been overwritten without ever being sent to a browser client.
Work Object PR_OTHER A work object has been saved to the PegaRULES database and stored as a row in the pr_other table, instead of the standard pc_work table or another table identified in a database table data instance.
Suggest Edit

100% found this useful


Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.