Missed task start rejected issue on 2016 Windows server - started 12/1/19

J

JFaulkner55

We have a task scheduled to run weekly on Monday - Friday at 6:00 pm (tried to include a screenshot, but it wouldn't let me submit with an image). It has been successfully running the 5 week days as scheduled. But starting 12/1/19, for some unknown reason the task is now starting on Sunday at 06:00 pm with the following warning message:


Task Scheduler did not launch task "\FeeTracking" as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed.


In the settings, we do not have the "run task as soon as possible after a scheduled start is missed" box checked. So I don't understand why this task is running on Sunday acting as if there was a missed scheduled start on Saturday which there was not.

This task was put into action on 11/13/19 and this issue started happening on 12/1/19. Any ideas on what is causing the task scheduler to think it has missed a scheduled start when it hasn't and why it is going ahead and starting the task even though the "Run Task as soon ...." box is not checked.

Continue reading...
 
Back
Top Bottom