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

Rule Not Found/Unresolved Assembly Errors In Production Logs



RuleNotFoundException is generated in the Pega logs.

Error Messages

[ ] [TABTHREAD1] [ ] [] (ngineinterface.service.HttpAPI) ERROR : PRRuntimeError
    at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt( ~[prprivate.jar:?]
Caused by: 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

Not Applicable

Root Cause

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.

Published April 10, 2020 - Updated December 2, 2021

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