Rule Not Found/Unresolved Assembly Errors In Production Logs
RuleNotFoundException is generated in the Pega logs.
[ ] [TABTHREAD1] [ ]  (ngineinterface.service.HttpAPI) ERROR : com.pega.pegarules.pub.PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:713) ~[prprivate.jar:?]
Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'PREPROCESSPAYMENT' that applies to 'Work-Interaction-Research'. There were 9 rules with this name in the rulebase, but none matched this request. The 9 rules named 'PREPROCESSPAYMENT' defined in the rulebase are:
9 unrelated to applies-to class '-Work-Interaction-Research',
Steps to Reproduce
A defect in Pegasystems’ code or rules.
The error occurred due to ChangeTracker cross thread evaluation.
As a local-change, set the Harness context to Propose context (as set previously) after expression evaluation.
This feature is implemented in Pega Platform 8.1.8.
0% found this useful