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

Advanced agent running on multiple nodes



An advanced agent is scheduled on two nodes and configured to run on only one node at a time. However, the the agent is running on both the nodes simultaneously.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create an advanced agent to send an email.
  2. Select the 'Run this agent on only one node at a time' checkbox in the Agent rule.
  3. Schedule the agent to run on two nodes.

Root Cause

This behavior is as per Pega product design.

Debug logging was enabled on the below classes: 
  • com.pega.pegarules.session.internal.async.BatchRequestorTask
  • com.pega.pegarules.session.internal.async.AgentQueue
  • com.pega.pegarules.session.internal.async.agent.QueueProcessor
According to the log messages, the Mutual Exclusion lock was obtained at 10:49:04,345 and released at 10:49:06,727 on Node 005. Then, Node 006 obtained the lock at 10:49:06,898 just after it was released.


Perform the following local-change to ensure the agent does not run for a period of time after it has run on one node:

Configure the 'Delay next run of agent across the cluster by specified time period' setting on the agent rule.

For more information, refer to:

Published September 6, 2019 - Updated December 2, 2021

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