Version

Argent Job Scheduler 10.0A-1306-A or below

Date

Wednesday, 11 Sep 2013

Summary

Addressed an issue with Argent Job Scheduler where a dependent Job runs when the Job it is dependent on is cancelled or abnormally ended

Technical Background

A dependent Job – say A – is set to run once the job it is dependent on – say B – completes with a specific exit code – example: 0 (normal end). But the Job A still runs even though Job B quits with a different exit code – example: 1067 (cancelled)

The issue occurs because the exit code of the dependent Job does not get properly updated in the database

The issue has been addressed in Argent Job Scheduler 10.0A-1309-A

Resolution

Upgrade to Argent Job Scheduler 10.0A-1312-B or later