Cisco Tidal 5.3.1 Job Group with (2) completed and the first job group (1) still waiting on Dependency.

[dhicks003]

We have a job group i.e. Job Group A that creates a second instance of the job group Job Group A (2) and completes normally. The problem is we have another job group that is dependent on Job Group A (1) so it never runs until we cancel the first job group or set it as completed. What could be inserting the Second occurrence of the JOB Group?  

[Derrick Au]

This sounds like a repeating job/group with new occurrences. Check out the Options tab for both group and job-levels

Group Options, If job is running, then Run Anyway

Job Options, If job is running, then Run Anyway

The correct setting should be:

Group Options, If job is running, then Run Anyway

Job Options, If job is running, then Defer until Normal or Defer Until Complete

which means if any of the deferred options are selected, the second occurrence will wait until job is completed normally (Defer Until Normal), or wait until job either completes normally or abnormally (Defer Until Complete)

Now I wonder what causes the second instance to complete normally and not the first instance.

BR,

Derrick Au