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

Issue with child requestor access group



You use queue method from an agent activity. The child requestor created to execute the queued custom activity has PRPC:Agents access group and hence the activity execution fails with a RuleNotFound error.

Error Messages Failed to find instance NYL-USIns-LTC-PAP-Work-IssueDecision.StartExceptionHandling for non personal RSLH

Steps to Reproduce

Configure an agent activity to call an activity using the queue method.

Root Cause

The child requestor uses the access group of the batch requestor which is defaulted to PRPC:Agents.


This issue is resolved through the following Local-change: 

In order to make the child requestor use the custom access group (using which the agent activity was executed), make the below changes to your agent activity:

Place the below java method in the agent activity just before the queue step and check the pass current parameter page check box when calling the queue method.

tools.putParamValue("pzUseCurrentAccessGroupForChild", "true");
tools.putParamValue("pzInheritRulesetList", "true");

Published June 12, 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