Skip to main content

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

Avoiding race conditions for advanced agents

Updated on July 8, 2022

To avoid race conditions associated with custom actions for advanced agents, make the actions thread-safe by ensuring that the agent runs on one node at a time.

Agent rules are no longer being actively developed; Queue Processor rules replace standard agents. For more information, see Using job schedulers and queue processors instead of agents.

  1. In the navigation pane of Admin Studio, click ResourcesAgents.
  2. Click the name of an agent that shows exceptions to open the agent in Dev Studio.
  3. For each agent, expand the agent record to display the Advanced area.
    Note: If you see a warning that agents will be deprecated, you can still modify the agent as described here.
  4. Configure the Advanced settings:
    • Select the Run this agent on only one node at a time check box.
    • Configure the agents to run on one node at a time at staggered intervals by selecting the Delay next run of agent across the cluster by specified time period check box.
    • Enter a time window during which to block agent actions in the Block execution within this time window fields.
  5. Click Save.
  6. Repeat steps 2 through 5 for each agent which was causing exceptions.
  7. Retest your application in a multi-node system.
  • Previous topic Associating an agent with a node type in a locked ruleset
  • Next topic Starting, stopping, and restarting agents

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