Async Job Group Dependency Overview

The Async Job Group Dependency feature enables you to create job group dependency chains. This is helpful for parallel processing, especially when you need a fork or join model.

The initial group in your dependency chain should always be a root job group. This is crucial because it provides a single record to lock, which prevents simultaneous processing issues.

How Async Job Group Dependencies Work?

• Group 1 contains jobs that execute in parallel.
• Once all jobs in Group 1 are complete, jobs in Group 2 and then Group 3 are executed.
• After Group 2 and Group 3 jobs are finished, Group 4 jobs are executed, and so on.

You can do this through the Job Group Dependency table, which includes these fields:

Job Group Dependency Table

Field	Description
ID	The record's ID.
Name	The system-generated name for the record.
Async Job Group	The ID of the ascendent (parent) job group.
Dependent Async Job Group	The ID of the dependent (child) job group.

To illustrate the example above, you should insert the following entries into the job dependency table:

Async Job Group Job

Async Job Group	Dependent Async Job Group
Group 1	Group 2
Group 2	Group 3
Group 3	Group 4

Notes:

• You can create dependencies at any point downstream in the chain. For example, a job in Group 2 could create more jobs within its current group and add additional dependent job groups.
• You need to be careful that you do not create cyclic dependencies in your Job Groups (for example, Group 1 having a dependency on Group 4). The system doesn't report these at insertion time due to the potential number of queries required, especially in complex chains.

Job Group Dependency supports both user mode and delegated system mode jobs. Dependent Job Groups are released as soon as the last job in the ancestor job group is complete. For more information, see Running Asynchronous Jobs in Delegated System Mode.