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.

Enabling or Modifying Agent Schedules (Data-Agent-Queue)

Updated on September 13, 2021

Understanding how to enable or modify Agent Schedules (Data-Agent-Queue) is critical to managing your Pega deployment effectively. This article explains the different approaches that you can take to enable or modify Agent Schedules in Pega 7.3 and Pega 7.3.1.

Consider reading the author's back story on this article and its companion articles, PDN Article collection on Agents.


Before you read this article, you should have fundamental knowledge of the Pega 7 Platform, especially the following Pega 7 concepts, tasks, and reference information:

  • How to develop rules for an application
  • Pega Agent concepts and terms and related topics
  • What Agents are available in Pega 7.3.1 and earlier releases and how to upgrade to Pega 7.3.1
  • How to create and schedule Agents in Pega 7.3 and Pega 7.3.1 on multiple nodes of a cluster (two or more Web Application Servers)
  • How to create, modify, and schedule Pega 7 Agent Queues
  • Information in the following PDN Articles:

Refer to Related Content for links to all prerequisite information and other references cites throughout this article.

Three approaches

To enable or modify Agent Schedules for your Pega 7 application, choose one of the following approaches:

Create Rule-Agent-Queue instances

  1. Create a new Rule-Agent-Queue (RAQ) in an application ruleset version.

The Master Agent wakes up at 10-minute intervals, detects a new RAQ, and creates the Data-Agent-Queue (DAQ), the Agent Schedule instance.

  1. You can now modify the DAQ without unlocking the ruleset so that you can change any of the following settings:
    • Pattern
    • Interval
    • Access Group
  2. For your updates to take effect, you must stop the Agents on the Agents landing page or in System Management Application and then restart them.

Update and migrate Rule-Agent-Queue instances

  1. Update Rule-Agent-Queue (RAQ) instances to include a new agent, a change in the agent or other attributes such as the following attributes:
    • Associated Node Type
    • Category
    • Mode
    • Activity
    • Parameters
  2. Change the Advanced settings:
    • Auto queue management
    • Running on one node
    • Delaying next startup time
    • Delaying the next runtime in the development (non-production) environment

The updated RAQ instances are then exported from the source environment and imported into the target environment. The Master Agent wakes up (10-minute interval), detects a change to the RAQ and updates or replaces the Data-Agent-Queue (DAQ), which is the Agent Schedule instance.

Any existing agent belonging to the ruleset is then updated (with the changes), removed (if removed from the RAQ), or skipped (no changes) with no user action required.

The Pega system then updates the System Management Application (SMA) > Agent Management > the Agents landing page with the changes introduced automatically.

Delete Data-Agent-Queue instances

  1. Delete the Data-Agent-Queue when there is an update to the Rule-Agent-Queue instances and you are not migrating the RAQ or the Ruleset Name and Version.
    Updates to the RAQ can include the following changes:
    • Include a new agent
    • Make a change to an agent
    • Other attributes (any combination of the first two updates)
  2. This requires a deletion of the corresponding Data-Agent-Queue (Agent Schedule) instances from the changed environment for the application ruleset associated with the agent.

The Master Agent wakes up (on a 10-minute interval), detects a change, and creates new Data-Agent-Queue (Agent Schedule) instances.

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