Reload Schedule - Skipping Date

[JustinDallas]

Hello Everyone,

I have a QMC task that was supposed to kick off at 08:01 AM this morning, but it didn't.  When I look at the Operations App, I see that the Reload chain was kicked off at 6AM, but not at the 08:01AM trigger.

Curiously,  when I look at the time for the next execution of my Task, I see that it says 6PM when it should really read 2PM

When I open the Trigger to see if something might be wrong with it, I don't find any reason for it to be skipped.

Does anyone have any idea why a Task might not be kicked off and in fact be skipped?  Also, this is the first task in a chain, so there are no preceding tasks that could have failed and stopped the chain.  Another thing to note, the server was not restarted during this period as I can see in powershell when the server was last Powered Off, Rebooted and the times don't match up.

Any help is greatly appreciated.

[rittermd]

Has this been running ok and just started to act up or is this the first execution of the tasks?

Have you verified time zones on your server?

Just in case this task is corrupted I would create a new one to kick off at some time and then verify that it started at ran at that time.  Just to try to narrow down the issue.

[JustinDallas]

Hello Mark,

Thanks for your response.  The task has been running ok, but I've just noticed that it skipped it's 8AM and had no intention of running it's 2PM as of today.  I will create another task and see what comes of that.

[rittermd]

The only time that I have run into issues with tasks not running at the scheduled time had to do with the setting for daylight savings time.  But that only threw it off an hour.  It didn't stop the task from running at all.

I gather from your description that there is no evidence that the job actually tried to run and failed?

[rittermd]

I just setup a test on my system.  I created a Reload task and scheduled it to run at 2:15 and then again at 2:22. 

It ran just as expected and the next execution is scheduled for tomorrow at 2:15

[JustinDallas]

The task actually DID run at 2 PM.  It leaves me curious as to why my 8AM was skipped.  I'll chalk this up to me seeing things, and assume that the problem won't reoccur, but I'll wade through the logs in the meantime.

Thanks for your assistance.

[Anonymous]

Log must be showing with different timezone, GMT may be. Compare the timezone differences across server time, GMT and your browser where you schedule the jobs.

I doubt it's not triggering on scheduled time or triggering on unexpected time. It's the logical miss from our end on times.