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 Log Error



User did a save as CPMPortalRecent in to their ruleset. When they are launching the portal, RuleNotFoundException is thrown in the log.


Error Messages

Not Applicable.

Steps to Reproduce

No steps to reproduce. Users see these error in the logs.

Root Cause

Tried to analyze the logs and GCS personnel saw that the context is switched to @baseclass somewhere and it is searching in that class.

But to analyze where exactly the context is switching and why, need use case and tracer for the error scenario.

Root vause was not identified as there is no use case. To remove the error from logs we can create an empty section 'CPMPortalRecent' into @baseclass as a work around.


Creating an empty section 'CPMPortalRecent' into @baseclass resolves the reported behavior.


Published July 28, 2016 - Updated December 2, 2021

Was this useful?

100% 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