Batch job chains

All batch jobs with the same ProcessId are considered linked to each other, and are known as batch job chains.

Batch job chains are processed sequentially by the batch processor. The processing order of batch jobs in a job chain is based on:

  1. The ascending order of their priority type code values.
  2. If the priorities are the same, then the order is defined by the ascending order of task definition ID values.
  3. If the priorities and the task definition IDs are the same, then the order is defined by the ascending order of task ID values.

Priority type codes and task definition IDs are contained in the XML task request, such as:

<PriorityType>100</PriorityType>
<TaskDefinitionId>80</TaskDefinitionId>

If one job in a batch job chain fails due to a runtime malfunction, the batch processor moves that task to the Stopped state, marks its action as Failed, and skips all the remaining jobs in the chain. Stopped batch jobs can be restarted later.

Tip: A batch processing instance can only process one batch job chain at a time. To enable processing for many batch job chains, you must either run more batch instances or run the same batch instance multiple times after the current run finishes processing.