Skip to main content

Best Practices

This page outlines best practices to ensure optimal performance, reliability, and maintainability when working for scheduled jobs.

Avoid scheduling jobs near daylight saving time transitions​

Every time-based job trigger may be affected by the transition into or out of Daylight Saving Time (DST). When the server clock moves forward or rolls back, jobs may trigger more often than expected, not at all, or at incorrect times during the transition period.

Recommendation​

Avoid scheduling jobs on the exact day and time of the DST transition to prevent unexpected behavior.

note

The specifics of DST transition hours and the amount of clock change vary by region. For more details, see Daily saving time by country

Example issues during DST transition (United States)​

If you schedule jobs in locations that observe DST—particularly on Sundays between 12:00 a.m. and 3:00 a.m.—you may encounter the following issues:

  • A job scheduled at 1:05 a.m. may occur twice when DST ends.
  • A job scheduled at 2:05 a.m. may not trigger when DST starts.
  • A job scheduled every 30 minutes from 12:00 a.m. to 3:00 a.m. may run two extra times when DST ends.
  • A job scheduled every 30 minutes from 12:00 a.m. to 3:00 a.m. may skip two executions when DST starts.