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.

Replacing an agent with a Queue Processor rule for delayed messages

Updated on April 5, 2022

Use Queue Processor rules for better performance and greater flexibility instead of agents. Replace an existing agent with a dedicated Queue Processor rule to process delayed messages, for tasks such as scheduling a review a week after a certain date.

Before you begin: Before you replace an agent with a Queue Processor rule, create the rule. For more information, see Creating a Queue Processor rule.
  1. Let the agent run until it resolves all the items that this agent queues.
  2. Create a dedicated Queue Processor rule.
  3. Disable a corresponding agent by performing the following actions:
    1. In the Dev Studio navigation panel, click RecordsSysAdminAgents.
    2. Select the agent that you want to disable, and then clear the Enabled check box.
    3. Click Save.
    Note: New delayed messages that a queue processor queues and messages from the broken queue are processed after a corresponding agent is disabled.
  • Previous topic Replacing an agent with a Queue Processor rule for real-time messages
  • Next topic Managing job schedulers

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