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

Incorrect (Withdrawn) Rule getting executed



Activity A called activity B.  A change was made so that Activity A calls activity C, and activity B was withdrawn. After the rules are migrated to the four production nodes, on one node, the version of activity A that called activity B is still used.

Error Messages

Not Applicable.

Steps to Reproduce

Call activity A on the various production nodes.

Root Cause

A defect in Pegasystems’ code or rules. 
When the rule changes were migrated to production, the cache on one of the nodes was not updated.  


User made the following prconfig, change to prevent the issue from happening again:

Set "systempulse/scanoffsetms"  to 30000. 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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