During the Daylight savings time jump from 2 to 3 this week-end, I found that any jobs schedules during the hour of 2 did not run, as time changed from 2 to 3.

Please add support for this, as well as the time change back in the fall, for those who use this.

Maybe some various options for this time, I havn't given to much thought as to what options at this point, but just to give an idea for some thought.

thanks

Jobs should normally be re-calculated if you have option "adjust for daylight savings" in Windows. Could you supply the server log for that change period.

---

Here is my log during the time change, it looks as though the recalculate worked, but not as I would intend. It seems like it recalculated for the next run on the 15th, instead of running the job that was missing because of the time change. If the job runs multiple times in that same day, it looks like, according to the log that it would be rescheduled for that day.

3/14/2010 1:58:21 AM Debug Number of running Jobs: 0
3/14/2010 1:58:21 AM Debug Number of running Tasks: 0
3/14/2010 1:58:21 AM Debug Log was trimmed from: 1076 to 1031
3/14/2010 3:00:00 AM Debug TimePutter: intDiff >=600 (3601)
3/14/2010 3:00:00 AM Debug Triggers will be recalculated due to time change in the system.
3/14/2010 3:00:00 AM Debug Next execution (6) for job 'Backup settings' is: 3/15/2010 2:00:00 AM
3/14/2010 3:00:00 AM Debug Next execution (6) for job 'Delete old log files' is: 3/14/2010 11:10:00 PM
3/14/2010 3:00:00 AM Debug Next execution (6) for job 'Elit Client Maint Window Automation Process' is: 3/14/2010 9:00:00 AM

thanks

Was the Job supposed to run between 2 and 3 or?

---

No, I did not suspend it.

thanks

What question did you answer to?

---

Sorry, I read it as suspend, not supose to run. And yes, there was a couple of jobs that should have run between 2 and 3, but where rescheduled for the next morning.

thanks

Can you elaborate more when the Job was supposed to run and which time the next run got?

Also, please tell us if this was a Custom or Interval Time trigger.

---

The main job in question was scheduled to run at 2:00 AM on the 14th of March. At 2:00 AM, the time changed to 3:00 AM, from looking at the VisualCron Job, VisualCron automatically reset the job to run at the next run time, which in this case, was on the 15th of March, at 2:00 AM. This is an interval scheduled job, to be ran daily at 2:00 AM.

I ended up having to run it manually, as I couldn't wait until the 15th when it was scheduled to run next.

thanks

Maybe we need to have some discussion how this should be handled best. There are a lot of exceptions regarding this. For example, let say your run your Job 4 times an hour between that time. Should we run the Job once then or 4 times?

Another problem is that 2:00 does not exist - it will just turn into 3:00. So, if a specific time does not exist how should we handle this.

The easy answer may be that we should have a setting that run any "missed" Jobs right after the time change. It is easier said and done and there may be a lot of opinions in how we should handle that - also, your case might not be the normal/generic case. Perhaps 3:00 is not a good time at all? Maybe it is better to just notify the user what happened?

Any input regarding this would be great.

---

I had this problem with another scheduling system and though it sounds flaky I have a practical solution.

2am is a special case for jobs that run on Sundays. Most timezones switch @ 2am for DST going backwards and forwards.

To avoid this problem..we scheduled things at 1:59am instead.

It's a quick solution, but not the right one.

I always account for this when I schedule my jobs... I just avoid scheduling during the times affected by DST to prevent jobs running twice or not being run at all.

I would think, if a job was suppose to run during that time that was missed, there should be an option to force the running of the job right away or wait till the next scheduled time. In this case, if the job runs hourly, you wouldn't care about running it, but if the job was daily, or weekly and so on, and was schedule for this time, you would want it to run right away.

thanks

My company experienced the same DST issue.

Reading through the thread I tend to agree with post #13. There needs to be some way for the job to run if it is missed. If it is not a built in function it should at least be a server setting or such that could be turned on.