Jobs didn't run for an hour after clocks went back for daylight savings time - VisualCron - Forum

Community forum

zettlemoyertsp
2020-11-01T13:14:57Z
Last night when the clocks went back one hour for daylight savings time, I noticed that none of my jobs ran during that hour. For example: I have jobs scheduled to run every minute, or every few minutes, and it appears that they all stopped and did not run for the hour after the clock rolled back. I'm guessing it's because VisualCron thought it had already run for that hour, which it did, but these recurring jobs should still have run again.

I understand that some jobs you might not want to repeat... but how do I make sure that some jobs do?
Support
2020-11-05T16:47:15Z
Originally Posted by: zettlemoyertsp 

Last night when the clocks went back one hour for daylight savings time, I noticed that none of my jobs ran during that hour. For example: I have jobs scheduled to run every minute, or every few minutes, and it appears that they all stopped and did not run for the hour after the clock rolled back. I'm guessing it's because VisualCron thought it had already run for that hour, which it did, but these recurring jobs should still have run again.

I understand that some jobs you might not want to repeat... but how do I make sure that some jobs do?



Currently this isn't possible,

I have moved this topic to feature request and notified our developers. We will let you know once we've made any adjustments/made it possible to run jobs for this.
Michael
Support
http://www.visualcron.com 

Please like  VisualCron on facebook!
Scroll to Top