In On-Prem workflow where can you see why a scheduled workflow did not run as a specific date and time passed?
Windows Task Scheduler. Each schedule creates a corresponding Windows scheduled task named using this pattern: WF8_<server name>_WF<workflow definition ID>_R<starting rule ID>.
You may have to turn on showing hidden tasks in Windows Task Scheduler. Then you can select the corresponding task and look at its History tab.
I found the tasks, but when I click on History it said Disabled. I clicked Enable and I do not see anything.
In the column view though, I see it says it triggers at 8am on day 1 of April, starting 4/1/2024 but then it says Last Run Time 11/30/1999 12am. Last run result is that the task has not run yet.
Now I am trying to find out why it did not run on 4/1/2024. The Windows system log likes to remind you that the time is accurate every minute of the day, so using this I could verify that the server was online at this time.
I Googled how to see when tasks are created, it seems you can not see which tasks were created when in Windows using any utility of any sort, but you can see when any tasks was created in general though the security log event 4698. Based on filtering for that event it seems that there has not been any tasks created after 5/1/2023 so all tasks were created before this time.
I am stumped, or should I say "fooled"
Any history wouldn't show previous to when you enabled it.
If you get info messages from Time-Service in the event log every minute, that might be an indication of problems keeping time. They're not expected to be that frequent. They're usually logged when the time is adjusted to match network time.
It is strange but I see no articles regarding excessive Time-Service posts. I asked on stack if we can have it only warn if there is a problem with the time, rather than logging every time the time is correct, which is all the time.
Unfortunately, I don't think the Subscriber Tracer shows things with scheduled rules, only condition rules (if you want to check anyway, you can go to Workflow Administration Console, select Monitoring > Subscribers, right-click the subscriber name and select Show Subscriber Trace Log).
Trying to review the history in the Workflow Designer is probably still your best bet. Even though the schedules do exist in the Windows Task Scheduler on the server, they all have names like WF8_SERVER_WF999_R999 and short of looking at the description on each one, I am not certain how to find a particular one (no search option that I can find), so if you have very many, this probably isn't a variable research option.
When this type of thing happened to us, it was because the time on the physical server was different from the time on the virtual server that was being hosted.