Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega application is slow and unresponsive at 3 PM AUS time



Application's performance degrades and does not respond between 15:00 – 15:10 Australia Time. This occurs on a daily basis.

Error Messages

Not Applicable

Steps to Reproduce


Root Cause

A defect in Pegasystems’ code or rules.

In the Alert logs, at exactly 5 AM GMT, multiple System calls occur to the below activities,
  • pzPersistSystemInfo
  • RuleUsageSnapshot
  • PushDBIndexes etc.

In the System Management Application (SMA), the following agents are configured to execute at 3 PM AUS or 5 AM GMT:

PegaAESRemote 2 PushDBIndexes
PegaAESRemote 3 PushGuardrailData
Pega-RulesEngine 0 PurgeAssemblyDatabaseCache
Pega-RulesEngine 6 PersistSystemInfo
Pega-RULES 3 RuleUsageSnapshot
Pega-LP 0 CalculateComplianceScoreDaily
Pega-LP 1 PurgeComplianceScores
Pega-LP 2 CalculateHistoricSpecificationData
Pega-LP 3 PurgeSpecificationData


Perform the following local-change:
  1. Configure all the agents to execute out of business hours such that they do not impact the users and the operations during work hours.
  2. Disable the agent using the below steps:

    Disable the PersistSystemInfo agent in the Agent Schedule for each node.

Note: The agent is already deprecated and not in since Pega Platform 7.3.

For more informaiton, refer to the following:

  • (Search for PersistSystemInfo agent. The agent is deprecated.)


Published August 19, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us