On the network I administer, I rarely come about problems with windows' task scheduler. But if I do, it's very annoying... the following has occurred: I noticed a task simply stopped to work from one day to the next, that is: it stopped to follow the schedule.
History: empty since the last successful start
Next run: empty (although it is set to run every day!)
->recreated the task, it worked for two days, on the third day it broke again.
This happened on different computers, different OS, different tasks, different executing accounts (normally: system) - no similarities. Several other tasks on the same computers keep working in the meanwhile.
Question: Since logging (=task history) breaks, too, what possible ways can I use to shed light on this? What lowlevel approaches apart from procmon could I use?