Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Agent processing throwing exception when run with an Activity

Updated on September 10, 2021



Some activities are executable only by authenticated requestors   You can set an activity to require authenticated requestors by selecting the Authentication check box on the Security tab of the activity:

When this check box is selected, the system ensures that the requestor calling this activity is authenticated before executing the activity. 

Since they are internal background processes, agents are not authenticated like interactive users are.  Therefore, if an agent process calls an activity that is marked for authentication, an exception similar to the following is thrown:

2007-09-25 05:00:22,426 [PegaRULES-Batch-6173] ( engine.runtime.Executable) ERROR - Only authenticated client may start this activity: RULE-OBJ-ACTIVITY @BASECLASS LOOKUPLIST #20070314T090210.050 GMT Error: You lack access required to execute RULE-OBJ-ACTIVITY @BASECLASS LOOKUPLIST #20070314T090210.050 GMT





If this security exception is detected, open the agent rule and check the Bypass activity authentication box of the agent rule that caused the exception.  When this box is checked, then the system does not look for user authentication on any activities called by the agents listed in this Agents rule.

NOTE:  The error message may not point to an actual agent activity.  (In the above error example, according to the error message, the activity “LookupList” has the problem.)  If the error occurs in an activity which is called by some agent activity, you may have to trace the process where the error occurred to see which agent activity is calling the problem activity.

After the agent activity is identified, check the box for the agent rule where that agent activity is listed.

In Version 5.3 SP2, this check box is located at the bottom of the Schedule tab in the Security section:

In Version 5.4, this check box is located on the Security tab:

The box is unchecked (disabled) by default.  If this box is not checked, then any agent activities (or activities called by the agent activity) that require authentication will throw the security exception described above.

Note that it is not possible to get access to change some agents.  If the RuleSet in which an agents rule is defined is locked (like the standard Pega- RuleSets), then you cannot change the rule directly.

In this case, check the Bypass activity authentication box on the Agent Schedule form.  Be careful to make this change to each Agent Schedule instance which exists for that Agents rule (on each node), so that the agent functionality is consistent across nodes in the system.

For further details, see Agents and agent schedules and How to modify an agent.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us