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

Latest version of a rule is not picked up after deployment



After deploying rules to production, the latest version of one (or several) of the rules is not picked up at run time.

This issue is sporadic and does not occur during each deployment.

Error Messages

Not Applicable

Steps to Reproduce

Deploy rules to production environment.

Root Cause

A defect in Pegasystems’ code or rules.

A race condition exists that can affect the system pulse agent and cause it to not process some of the rules.

The issue is more likely to occur when importing a large number of rules.


Perform either one of the following two local changes to add a delay to pulse processing in milliseconds and to prevent the issue from occurring in the future.

Note that the value of 60000 is in milliseconds and is equal to 1 minute.

To fix the currently affected rules, run Revalidate and Save (Designer Studio > System > Release > Upgrade > Validate > Revalidate and Save).

and add the following line to the prconfig.xml file:

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


a) Add a dynamic system setting (DSS) with the following:
  • Short description: prconfig/systempulse/scanoffsetms/default
  • Owning Ruleset: Pega-Engine

b) Add 60000 as the Value and click Save button.

Published July 10, 2017 - 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