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

Changes made to one environment not reflecting in other



A change was made to a Data-Admin-Keystore instance in one Pega node (uploaded a new Jks file and saved it).

The same Keystore record when viewed from another Pega node does not reflect the update.

Error Messages

Not Applicable

Steps to Reproduce

In a multi-node environment, make a change to a Data-Admin-Keystore rule, and see if the change is reflecting in all the other nodes.

Root Cause

A defect or configuration issue in the operating environment.

HFix-24531 was installed for caching keystore instances to improve performance but the associated trigger trpr_dataadm was missing in the database.


Make the following change to the operating environment:

Ensure that the trigger
trpr_dataadm is present and running correctly in the PegaRULES database.
Suggest Edit

Published November 3, 2017 - 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