Support Article
RuleNotFound error after migration
SA-35382
Summary
After migrating rules to a new environment, errors occur when the rules are invoked after migration. The error vanishes after a cold restart with cache clear.
Error Messages
2017-03-17 10:12:37,811 [fault (self-tuning)'] [ STANDARD] [ ] [ RULESET:01.04.01] ( internal.mgmt.Executable) ERROR NODE.ADDRESS|127.0.0.1|Rest||||A78C65436A45B61D83792B1CBCD131D1C - Exception com.pega.pegarules.pub.PRRuntimeException: Interaction type RunInteraction failedSubscription'
Steps to Reproduce
Migrate rules from one environment to another and the error occurs intermittently.
Root Cause
A race condition can occur if the system pulse agent is not configured properly in some multi-node systems, causing the system pulse agent to not properly synchronize new rules across the nodes. If not addressed, a restart is required to synchronize rules when this occurs.
Resolution
This can be addressed by using the following system setting:
Create the following dynamic system setting:
Owning Ruleset: Pega-Engine
Setting: prconfig/systempulse/scanoffsetms/default
Recommended Value: 30000 (milliseconds)
Published March 26, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.