After setting the clocks to Standard Time a scheduled job runs an hour earlier although the time of the server has been correctly changed. Example: Scheduled job is defined for 2.30 pm, but now runs at 1.30 pm.
Question
After setting the clocks back to Standard Time a scheduled job runs an hour earlier
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
This behaviour is expected if a schedule is based on an interval due to the underlying library for the scheduler. If 'Interval Based' is specified, the schedule does not adjust when switching between Standard Time and Daylight Saving Time. We added this information to our documentation: https://docs.safe.com/fme/html/FME_Server_Documentation/Content/WebUI/Adding_a_Scheduled_Task.htm?Here is some additional information: http://www.quartz-scheduler.org/documentation/faq.html#FAQ-daylightSavingsFor jobs that have to run at an exact time of the day, I recommend using a CRON expression instead of the interval. This resource describes some best practices:
http://www.quartz-scheduler.org/documentation/best-practices.html#daylight-savings-time