Support Article

Scheduled Agent called but SQL Connect not executed



A scheduled agent is configured to run an activity to execute several Connect SQL calls.  

After the scheduled time has passed, the state of the database indicates that the Connect SQL calls were never executed.

If the activity is executed manually, the Connect SQL calls execute successfully.

Error Messages

30 Nov 2016 09:34:00,019 [ PegaRULES-Batch-2] ( async.agent.QueueProcessor) DEBUG - No item to process: MyAgentRuelset #1:  MyOrg-MyParentClass-MySubClass.MyAgentActivity

Steps to Reproduce

Execute an standard agent who's agent activity makes one or more Connect SQL calls.

Root Cause

An issue in the custom application code or rules where the agent was created with a mode of "Standard", however no queue items were present.

This resulted in the agent activity not being executed when the agent ran.  In "Standard" mode, at least one queue item is required for the agent activity to execute.


Perform the following local-change:

​Adjust the agent to use "Advanced" mode, which will run the activity when the agent runs without the need for any queue items.

Published December 9, 2016 - Updated December 19, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.