Daylight Saving Time Update: What to Expect for Scheduled Tasks

What’s changing
When Daylight Saving Time (DST) begins in March, clocks move forward by one hour. This creates a “missing hour” in local time (for example, 2:00–2:59 AM does not exist).
Historically, this time change has caused issues for scheduled tasks in DST-observing time zones. To ensure reliable behavior this year, we are implementing an updated approach for how task triggers behave during the DST transition.

How task triggering will work

• Tasks scheduled in time zones that observe DST will continue to run aligned to local time before and after the time change.

• The single missing hour created by DST will be skipped.

• Tasks will not attempt to run during that non-existent hour.

• After the clock moves forward, schedules resume normally with no ongoing time drift.

Example:

• A task scheduled hourly will run at 1:00 AM, skip the missing DST hour, and then resume at 3:00 AM local time.

• Daily tasks scheduled during the missing hour will not run that day but will resume at the correct local time the following day.

Why we’re doing this
We evaluated multiple approaches and identified that:

• Attempting to execute tasks during the missing DST hour can cause system instability, including infinite scheduling loops that require manual intervention.

• Skipping the non-existent hour is the safest and most predictable behavior, preventing failures while preserving correct local-time scheduling.

This approach ensures:

• No infinite loops

• No permanent schedule shifts

• No long-term timing drift for customers

What customers should know

• Only one hour is affected, once per year when DST begins.

• This impacts only schedules set during the missing DST hour in DST-observing time zones.

• No action is required unless customers want to adjust schedules to avoid the DST transition window.

Ongoing improvements
In parallel, our engineering team is upgrading our scheduling engine to the latest stable version. We are evaluating whether newer releases fully resolve DST edge cases and will continue to improve this behavior in future updates.

Need help?
If customers have workflows that are highly sensitive to exact execution times around DST, Customer Success can help review schedules and recommend adjustments.