LinkedIn
Copied!

PEGA0013 alert: Activity interaction time exceeds limit

When a service rule receives and processes a request, the system runs a service activity after the request data is mapped. The PEGA0013 alert is triggered when the elapsed time required for running the activity exceeds the threshold setting.

As of version 5.3, this alert and its corresponding settings are deprecated. Elapsed time for response mapping is included within the elapsed time reported in the PEGA0011 alert.

Example message text

Service activity interaction time has exceeded the threshold of 500 ms: 9072 ms

Default prconfig.xml settings

<env name="alerts/services/activityTime/enabled" value="false" />

Toggles the alert on ("true") or off ("false").

<env name="alerts/services/activityTime/threshold" value="500" />

The default threshold setting is 500 milliseconds (1/2 second).

This setting measures elapsed (total) time, not just CPU time.

Reason for the alert

If the service activity is taking too long to run, examine or trace the processing of that activity. Make sure that it is not calling too many other processes, such as activities or when rules.


Related Content

Have a question? Get answers now.

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