Support Article
RuleNotFound Exception when running Agent
SA-13490
Summary
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:
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:706)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:567)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:425)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:259)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:322)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:884)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1192)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:930)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:829)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:617)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:744)
[...]
Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException:
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.
Resolution
After adding correct Access Group for Batch Requestor the exception no longer occurs.
Published August 28, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.