11-06-2015 11:30 AM - edited 03-01-2019 09:18 AM
I have noticed that if I disable a job that already has been forecasted, the disable function no longer pulls that job from schedule.
Ex: Disabled Tech_*** job on 11/2. On 11/5 the job completed abnormally, yet the database still has job as disabled. In our previous version 5.3.1, it would yank all scheduled version of that job out once disabled. Any ideas how to make it do that again?
01-05-2016 10:17 AM
Hi hrechek4470,
We are running Tidal 6.0.2. If you delete the job the job will be removed from the forecasted schedule. When disabling a job the job will remain in the schedule for as many days the job has been forecasted, we manually go to Schedules and Remove Job(s) From Schedule and click All, this should remove the job from the forecasted schedule.
01-05-2016 10:32 AM
It used to function that way. We found that this was a glitch that was fixed by a newer version. Upgraded to 6.2.1.367 and it was resolved.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide