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 resolution errors on running application



Rule resolution errors occur on running application.

Error Messages

Failed rule resolution errors

Steps to Reproduce


Root Cause

A defect or configuration issue in the operating environment. The population of the vtable cache for some of the rules was incorrect due to the thousands of dropped database connections. The cache contained an entry for a rule that said 'this rule does not exist'  when the attempt to retrieve the rule (upon initial cache entry creation) failed. According to the cache code, the rule in question did not exist because of the dropped database connections. Hence, the cache entry was marked accordingly. Subsequent attempts to access the rule stopped at the cache lookup with the RULENOTFOUND error. A clue to this situation was found in the Tracer cache event which said 'Cache Hit (not found)', indicating that the rule did not exist. The rules were present in the database and were accessible.


Perform the following local-change:
Resave one of the affected rules. 
See Troubleshooting rule resolution issues.


Published March 29, 2019 - 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