Disabled job executed when the job it is dependent on is deleted.

[john.schmidt]

We had Job1, Job2 and Job3.   Job3 is dependent on Job2 and Job2 is dependent on Job1.  All three jobs were disabled!  I deleted Job3, no issues.  I deleted Job1 and Job2 ran because the dependency on Job1 had been removed but the deletion of Job1 but all jobs were disabled!!  I deleted Job2 and then found it had launched on the resident system. 

Why would a disabled job launch?   It looks like the workflow checks for dependencies before checking if the job is enabled and if dependencies are met it runs the jobs. 

Again none of the 3 jobs were on the schedule because all were disabled over a week ago on 5/25!?!?

Please review and advise/

Thanks,

John

[jeff.hamway01]

Hello John,

It always helps to post what version of Workload Automation you are using and what environment your running in.  either way,  it does sound like  Job 2 was still being scheduled. 

- Check your schedules under the Operations navigator from the day the unscheduled job was run and see if it was scheduled. 

- My environment is set to build scheudules 6 days in advance.  check your Future days setting in system configuration.

-  If needed you can rebuild schedules

- check the logs to see if JOB B is actually being loaded

/got nothing else at this time. 

Jeff

[john.schmidt]

We are on Tidal 6.1.0.368