Symptoms

When a Job Trigger is configured to wait for an instance in the same cycle as the dependent job, the job may be incorrectly triggered for an instance of the target job that is not in the same cycle.

Cause

adTempus may fail to reset its tracking of dependency jobs when the cycle ID is updated, causing it to think that the trigger rule has been satisfied. This occurs when a dependency job is run "out of cycle."

Status

• adTempus 4
  This issue has been resolved. Resolved in version 4.4.