Running a schedule in a time zone
Configuring your schedules according to the specific time zone in which they need to operate is important for effectively managing your scheduled tasks across different time zones. This ensures consistency and accuracy, particularly during daylight saving time transitions, so your scheduled tasks can run smoothly without any unexpected shifts.
There are two ways to set a schedule in a time zone:
Scheduler time zone: If you want to use a time zone that differs from the browser time zone or model time zone, you can configure it directly within the schedule. This allows you to assign varying schedules to different time zones as needed.
Note
A browser time zone refers to the time zone setting configured on a user's device or browser. It is automatically determined by the device’s system settings and can vary based on the location of the user.
By default, Scheduler takes the current browser time zone of the user and displays all scheduled tasks in that time zone. If no specific time zone is assigned to a schedule, the browser’s time zone becomes the default reference point.
Model time zone: You can create a schedule that adheres to the model's time zone. For example, if the model's time zone is set to PST, the schedule will automatically follow that time zone.
To learn more, read: Setting a model time zone.
Daylight savings time adjustments
The time zone settings will account for daylight saving time. According to the daylight savings schedule observed in the specified time zone, the system will automatically adjust the clock forward by one hour in the spring and revert back by one hour in the fall. Only the time zones observing daylight savings will experience these updates.
To set a time zone in the Scheduler module:
From the Scheduler module, click Create to create a schedule.
From the General tab, enter a name for the schedule.
From the Frequency section, turn on the Add run toggle to run this schedule automatically on a set frequency.
Configure the schedule to run at a daily, weekly, monthly, or yearly frequency at any designated time.
From the Time zone section, turn on the Run schedule on a different time zone toggle to run the schedule on a time zone other than your browser's or model's time zone.
Select a time zone from the dropdown.
Note
This time zone will be applied to all tasks and folders in the schedule.
Note
If you set a run time that coincides with the daylight saving transition of the selected time zone, your schedule may either repeat or skip the task. In this case, a warning message will alert you when setting the time zone, indicating potential effects on your schedule during transitions. To avoid this, consider adjusting the run time.
Read Running a schedule during daylight saving time transitions to learn more.
Turn on the Run imports in parallel toggle if you want to run multiple imports within the same folder simultaneously.
Note
Adding non-import tasks to this folder will disable the ability to run parallel imports.
Click Save.
When you save a schedule with a specific timezone, it will appear in the All schedules panel along with the timezone stamp.
Running a schedule during daylight saving time transitions
When you decide to run a schedule in a time zone different from your browser's or model's, it's important to understand how Daylight Saving Time (DST) affects the schedule.
Important
If you don’t explicitly set a time zone and rely on your browser’s default time zone, it will not automatically adhere to daylight saving transitions. In this case, you must manually set the same time zone for your schedule so the system can follow DST changes accurately.
When you set a time zone in the Scheduler module or across the entire model, it will automatically adjust to the Daylight Saving Time (DST) of the specified time zone. However, if you set a run time that coincides with the DST transition, your schedule may either repeat or skip the task. A warning message will alert you when setting a time zone, indicating potential effects on your schedule during transitions. To avoid this, consider adjusting the run time.
For example:
Imagine you're setting a schedule to run every Sunday at 2:30 a.m. when you're in New York, which observes DST.
In March: On the second Sunday, when DST starts at 2:00 a.m., clocks spring forward to 3:00 a.m. If your schedule is set for a run time at 2:30 a.m. on this day, the system sees this as a non-existent time due to the jump. Consequently, the schedule will run immediately after the transition at 3:00 a.m. if no adjustment is made.
In November: On the first Sunday, when DST ends at 2:00 a.m., clocks fall back to 1:00 a.m. Your schedule set at 2:30 a.m. will occur twice - once before the rollback at 1:30 a.m. and once again after the rollback if unchecked.
Action steps:
For the March transition: Adjust the schedule to run at 3:30 a.m. to prevent a skip during the spring transition.
For the November transition: Adjust the schedule to run at 1:30 a.m. or 3:30 a.m. to avoid duplication during the fall transition.