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

Updated rule not retrieved post Pega product file deployment



The updated rule is not retrieved post Pega product file deployment. However, this is resolved only by a clear cache restart.

Error Messages

Not Applicable

Steps to Reproduce


Root Cause

A defect or configuration issue in the operating environment.

After an import, the system pulse is responsible to retrieve the new rules. Update the caches accordingly and perform a sync across all nodes.


Perform the following local-change such that a restart is not required during an import.

Add the following setting in the prconfig.xml or through the Dynamic System Setting (DSS) in Designer Studio. Adding this setting requires a restart.

<env name="systempulse/scanoffsetms" value="30000" />

This ensures that all the rules are processed during the import.

In case the rules are not retrieved due to issues with the cache, perform the following instead of a restart,

  1. Navigate to System Management Application (SMA) and select an affected Node. Click Advanced.
  2. Click the Virtual Rule Table Cache Management. Enter the rule class and instance name (which are not retrieved).
  3. Click Lookup Virtual Cache table detail. Click Reassemble Candidates. This rebuilds the cache and the rule is now available.

Published July 23, 2018 - 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