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.

​

Runbooks have the ability to alter the end time of tasks that are affected by daylight savings time. 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.

During daylight savings, if time has moved forward by one hour, that hour will be added to the end time of the task that is affected at the point of the time change. As a result, the previously scheduled one hour task duration will last two hours. If the time has been pushed back by one hour, the end time for tasks that are active during this change will be set at the time the task was started.

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.