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

DSM Proposition sync across nodes not work in Pega 7.2.1



Decision Strategy Manager (DSM) uses System Pulse to synchronize Proposition changes across the nodes, which is not working in Pega 7.2.1. Proposition pulse handler is not registered at PRPC node startup. Changes made on first node should visible on second node Proposition Landing page on refresh, which is not the case.

Error Messages

Not Applicable

Steps to Reproduce

  1. Add the PegaDM: Administrator access group to the Batch Agent in the Systems, Nodes and Requestors landing page.
  2. Launch the PLP on two nodes in PRPC cluster: Designer Studio > Decisioning > Decisions > Proposition Management > Propositions data
  3. Edit proposition on the first node.
  4. Refresh PLP on the second node.

Root Cause

Proposition sync rely on System Pulse to communicate the changes made on one node to other nodes in Pega Platform cluster with help of registered Pulse handler’s library. Due to recent changes made in the core-engine layer to defer the compilation of library at PRPC startup, Proposition Pulse handler’s library is not registered at PRPC startup, which was happening in the previous releases.


Apply HFix-29438.

Published October 13, 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