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

SLA agent fails due to RuleNotFoundException



An assignment is configured with a Service Level Agreement (SLA) that invokes an Escalation activity to complete the assignment. Intermittently, the SLA agent fails when processing the queue items.

Error Messages

Flow <FlowName> had an error in step Utility5: Failed to find instance <ClassName>.<ActivityName> for non personal RSLH 5004c59f74192a820954e3b9ae0d5f7d Top App Hash PegaRULES!en_US_!PRPC:Agents!06.03$2ee6c141136e77e062a1187848bbb670 of type Rule-Obj-Activity.
Trying to save an invalid page: page is not valid

Steps to Reproduce


Root Cause

In this case, a commitwitherrorhandling step in the application activity could cause the SLA agent to lose the context.

A similar error was reported in this Support Article:


As a local-change, delete the Commit step.


Published November 29, 2018 - 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