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

Standard agent runs repeatedly not taking the schedule



When a standard agent is configured to run periodically and based on a condition will re-queue the same work object back to itself, the re-queued item is picked up immediately instead of waiting for the next interval on the agent schedule.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a standard agent with Periodic schedule.
  2. Create an agent activity with a condition that if not met will cause the case to be re-queued to this agent.

Root Cause

An issue in the custom application code or rules.


Here’s the explanation for the reported behavior: 

This is the expected behavior as the re-queue configuration used makes the queue item available immediately to an actively running agent which will pick up the new queue item before going to sleep and waiting for the next period. To a
void this sequence, place an allotment of time in the MinimumAgeForProcessing field for the method queueforagent as described on the following PDN article: This will cause the queue entry to not be available until the agent goes to sleep and won't be picked up until next run time.


Suggest Edit

Published March 25, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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