Troubleshooting: schedules with Daylight saving time (DST)

If you have selected a timezone with Daylight saving time (DST) changes for your schedule, the transition of Daylight saving time affects the execution schedule since a time interval is repeated or skipped on the day of change, and thus the next actual execution is adjusted accordingly.

For example, a task run is scheduled to be triggered every 20 minutes with the latest run happening at 01:40:00. With this schedule, next execution time is set to 02:00:00.

However, during the DST change, the clock moves back from 02:00:00 to 01:00:00, repeating the hour between 01:00:00 and 02:00:00. Therefore, the next scheduled execution does not happen immediately at the end of the next 20-minute timeframe, even though it appears that 20 minutes have actually passed since the previous trigger at 01:40:00. The subsequent triggers at 01:00:00, 01:20:00, and 01:40:00 are ignored, and the task is triggered only at the adjusted 02:00:00 time after the transition.

Procedure

If this behavior is an issue for your schedule, use a timezone that does not include any Daylight saving time changes, such as the Coordinated Universal Time (UTC) timezone.

You can use this endpoint to accomplish this when creating your schedule.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here