More about Agent Schedule data instances
 

Changes

After you save a modified agent schedule, changes take effect only after the Agent Manager master agent notices the changes. By default, the Agent Manager checks for manually updated agent schedules (and new and updated agents rules) every 10 minutes.

Starting and stopping agents

Normally, all agents start each time you start your Process Commander system. Agents running on a specific node start as that node starts. When testing or otherwise necessary, you can use the System Management application to monitor or control agents:

1. Start the System Management application.
2. Select a node.
3. Select the Agent Management menu item.
4. Click a single radio button to identify a thread of an agent. (Each agent activity executes in a separate thread.)
5. Use the buttons at the top of the page to start the agent, stop the agent, or pause agent processing. You can affect only the selected activity (one row of the form) or all activities.

Agent Schedule instances and the system name

The Node ID is a key part of each agent schedule data instance. If you change the system name, all node IDs also change, so new Agent Schedule data instances are created at startup. When the name change is complete, you can delete the older Agent Schedule instances, which are no longer in use.

See When and how to change a system name.

For more information

The Pega Developer Network has many articles about agents and agent processing including:

• PRKB-25156 About Agents
• PRKB-25248 Enable legacy agents on only one node of a multinode cluster
• PRKB-21572 Troubleshooting agents.

	Agents — Concepts and terms About Agents rules About the System Management application
	Atlas — Initial Agent Schedule data instances

About Agent Schedule data instances