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

New rules are not synched up across nodes after code migration



After code migration  migrated rules are not being picked up until the cache is cleared and all nodes are restarted.

Error Messages

The migrated rules are not being picked up

Steps to Reproduce

1) Setup a multinode environment
2) migrate the code 
3) verify if the changes are reflecting in the same node which is used to migrate the code
4) Now check the other node and observe the changes are not reflecting when user login to the application from other node


Root Cause

The system pulse was not running when code was migrated last time.

System pulse informs the othernodes there is a rule change happened in a particular node and other nodes should update there cache accordingly by querying the pr_sys_updatecache table


Migrated the code again with system pulse running and there is no issue observed.

Published January 31, 2016 - 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