Check the job log. In the job log it should say what was wrong and why the job was disabled. In version 2 the default is to disable jobs after critical errors. You can change this option on the job level. : Running version 2.4.15. We get random occasions where a job : (we run approx. 12 jobs each 24 hours) suddenly, out of nowhere, : shows up as disabled. This happens at very irregular times, : without any pattern, to different jobs, at varying times of the : day, etc. : Example: a job runs at 9:10 every morning, 7 days/week. : At 8:40 am, the schedular looks perfect. I return at 9:30 am, : and the 9:10 job didn't run, and the job shows as disabled. I : enable the job then and "Run now". The job runs perfectly and : remains enabled. No previous error messages; the job had been : running w/o error for weeks, maybe months before this happens. : Any and all suggestions welcomed. TIA.
|