Skip to main content

PEGA0107 alert: Client page load time for offline-enabled applications

Suggest edit Updated on January 19, 2022

The PEGA0107 alert is generated when the total elapsed time from when the user clicks to when the screen has finished being rendered exceeds the configured threshold (in milliseconds). The PEGA0107 alert is an equivalent of the PEGA0069 alert in the context of offline-enabled applications, and PEGA0069 is not generated for offline-enabled applications. Operations that contribute to page load time in offline-enabled applications are different than the ones for regular applications. For example, network and server operations do not occur, while client database access operations are frequent. Templating, databinding, and JavaScript processing operations are common contributors to page load time for both types of applications.

Example message text

ClientPageLoad has exceeded the elapsed time alert threshold of 4000 ms, total duration 5116 ms, load description action:openWorkByHandle|key:AAA-APPPA-WORK C-1|.

Changing the trigger value

You can override the default setting of 4000 ms:

  • on all nodes in a cluster, by adding the Dynamic System Setting. Restart all nodes for the changes to take effect,
  • on one node, by changing the prconfig.xml file that resides on the node that you want to modify.

You can disable the alert by changing the setting to a negative value.

Dynamic System Setting

Owning ruleset: Pega-Engine

Setting purpose: prconfig/alerts/browser/clientpageloadtimethreshold/warnofflinems/default

Value: <threshold in milliseconds>

Default prconfig.xml setting

<env name="alerts/browser/clientpageloadtimethreshold/warnofflinems" value="4000" />

The threshold value is in milliseconds. The default value is 4000 milliseconds.

Probable reasons for alert

If your alert log contains a large number of PEGA0107 messages, a problem on the client might be causing screens to take a long time to load. Using the message text, compare the load duration to the database access duration, templating, databinding, and JavaScript processing duration to identify the root cause of the issue. The action specified in the alert message can also help you determine which screen or action caused the alert.

Other alerts that are triggered by this screen load have the same requestor ID and page load counter as the PEGA0107 alert. You can use this information to correlate those alerts to the PEGA0107 alert.

Monitored offline operations

Action CategoryMonitored Actions
Process Work
  • Add new work
  • Finish assignment
  • Save
  • Harness
Get Work
  • Create work
  • Open assignment
  • Open work by handle
  • Refresh harness with data transform
Did you find this content helpful? YesNo

0% 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us