Runbooks have the ability to alter the end time of tasks that are affected by daylight savings time. In this article, we'll cover changed task duration and dual time zones during daylight savings time.
Changed task duration
Runbooks can automatically adjust task end times affected by daylight savings time. These adjustments are calculated when a runbook is scheduled or while tasks are running.
When clocks move forward by one hour (e.g., start of daylight savings):
The end time of tasks active during the change will account for the lost hour. For instance, a task with a scheduled duration of one hour will effectively span two hours.When clocks move back by one hour (e.g., end of daylight savings):
The end time of tasks active during the change will align with the task's start time. For example, if a one-hour task starts at 2 AM and clocks move back by one hour, the task will end at 2 AM (after the time adjustment).
Note: Whether daylight savings changes occur before or after a runbook has started, you are able to view task scheduled start/end times, and task duration via the task list.
If a runbook has a default timezone that is not affected by daylight savings time, all tasks will remain unaffected and will continue to operate on schedule.
Dual time zones
In the event you are viewing a runbook from a region outside of the runbook's default timezone, there will be two separate time stamps marking the time difference next to tasks in the task list. One timestamp displays time in the runbook's default timezone, while the other displays the time in your region.
Daylight savings changes will not affect the timezone of a user who is not experiencing a time change. This means that tasks will continue to run and finish at their expected time.
If a runbook is started prior to a time change, the header timezone will remain unaffected until the runbook is completed.