Dependency Mapper Error After Moving or Adding Agent


Article ID: 5469


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


When trying to execute a deployment against agents of a particular server type, the deployment fails with the following error:

Unexpected error on server [Could not find all needed dependency mapping needed to create a process run. unsatisfied links (sourceJobServerId-->targetServerTypeId): {3605496=[3010419]}. Please Select one agent for the server type(s): [st1]]. Please refer to server logs with timestamp [2017-01-04 00:37:53].


If this error occurs after verifying that the involved agents are correctly assigned to their respective server types, then the error means that dependency was broken when an agent moved from one server type to another.

Understanding this cause requires some illustration.  Consider the following example: a process employs more than one server type. For this example we will refer to these as "ST1" and "ST2" (Server Type 1 & 2).  The process includes an action or flow associated with ST1 progresses into another action or flow associated with ST2.  Each server type has multiple agents assigned to it.

For this example, we will assume the following:

  • ST1 consists of agents AGN1, AGN2, and AGN3.
  • ST2 consists of agents AGN4 and AGN5.
  • FLOW1 within PROCESS1 is associated with ST1.
  • FLOW2 within PROCESS1 is associated with ST2.

The above scenario will allow for a successful deployment.  Next, however, consider if one of the following changes is made:

  • A new agent is assigned to ST2.
  • An agent belonging to ST1 is reassigned to ST2.

In the above scenario, after the change, the deployment will fail with the error in question because no dependency was defined for the agent after it was added or moved.


Release: NOLNAC99000-6.1-Nolio-Automation Center


  1. Launch and login to Automation Studio.
  2. Navigate to the Design tab at the bottom.
  3. Select the affected application in the drop-down menu.
  4. Navigate to the Processes tab at the top.
  5. Locate the affected process.
  6. Click the "Publish and Run" button.
  7. Select all agents the process should use under the "Servers" tab.
  8. Click the "Dependencies" tab.
  9. Set dependencies accordingly.
  10. Let process complete running.
  11. Return to ROC.
  12. Go back to the deployment, then run it again. It should run successfully.