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

RuleNotFound Exception when running Agent



Activity triggered by property change (using Declare Trigger) fails with RuleNotFoundException.

Error Messages

[ PegaRULES-Batch-22] [ STANDARD] [ ] [ PegaRULES:07.10] (ernal.async.BatchRequestorTask) ERROR - Batch activity "<your activity named>" threw: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
Caused by:

Steps to Reproduce

1. Create agent which fires an activity and make sure the property changes during execution.
2. Create new Declare Trigger against this property and run the agent.

Root Cause

Since the Activity is in a custom ruleset, it is necessary to alter the Access Group List for for Batch Requestors to include this RuleSet. 


After adding correct Access Group for Batch Requestor the exception no longer occurs.


Published August 28, 2015 - Updated October 8, 2020

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