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

Agent does not run on multiple nodes

SA-85546

Summary



After modifying the Node classification, agent processing that occurred on multiple nodes only processes on a single node.


Error Messages



Not Applicable


Steps to Reproduce



Queue multiple work objects for processing through an agent.


Root Cause



A defect or configuration issue in the operating environment.

The agent performing the processing was not associated with all the node types it was intended to run on.


Resolution



Perform the following local-change to associate the agent with the desired node types: 
  1. Click Designer Studio > System > Operations > Node Classification.

  2. On the Agents tab, click +New association for the agent to which a node type must be added.

  3. Select a node type from the list. The agent runs for all the nodes that are started with the node types associated with the agent, including the node type that is added.

    • RunOnAllNodes – The agent runs on all the nodes in the cluster that are started with any node type, regardless of the node classification.

    • Search – The agent runs on a search node for search jobs.

    • WebUser – The agent runs on a web user node for web user jobs.

    • BIX – The agent runs on a BIX node for BIX jobs.

    • Custom1, Custom2, Custom3, Custom4, Custom5 – The agent runs on the selected custom node.

  4. Remove the new association by editing the Agent schedule rule (optional).
For more information, refer to: https://community.pega.com/sites/default/files/help_v73/procomhelpmain.htm#engine/Node%20Classification/eng-associating-agent-with-node-type-in-locked-ruleset-tsk.htm
Suggest Edit

Published December 6, 2019 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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