Impact of Daylight Saving Time on Salesforce Scheduled Jobs

How Salesforce Handles Daylight Saving Time for Scheduled Jobs

Salesforce stores and executes all scheduled job times in Greenwich Mean Time (GMT), not in local time. This means the underlying schedule does not change when DST begins or ends — the job continues to run at the same GMT time regardless of the local clock adjustment.

Impact on Daily and Higher-Frequency Automations

For automations that run daily or at longer intervals, the scheduled execution time adjusts automatically to reflect the user's local time after DST transitions. This means that if you scheduled a job for 1:00 AM local time before DST ended, it continues to run at 1:00 AM local time (the new UTC offset) after the transition.

Impact on Hourly Automations

For automations that run hourly, the schedule does not adjust for DST. The job continues to run at the same fixed interval in GMT, which means the local time display shifts by one hour after a DST transition, but the job does not run twice or get skipped.

Example: GMT Offset Shift During DST

Consider a user in a timezone that is GMT+5 during DST and GMT+4 after DST ends. If they schedule a job for 1:00 AM local time (which is 8:00 PM GMT the previous day), the job runs at 8:00 PM GMT regardless of the DST transition. After DST ends and the offset changes to GMT+4, the same 8:00 PM GMT execution time displays as 12:00 AM local time to the user — one hour earlier in local terms — but no time travel or double-execution occurs. The GMT offset changes, but the GMT execution time remains constant.