When a Runbook Admin sets a Fixed Start Time on a task, the task is locked and cannot be started by assigned teams or users until the specified date and time— even if all predecessors are complete. Admins can override this and start the task early if needed. This “True” Fixed Start Time behavior ensures greater control and precision during execution.

In this article, we will go through what is “True” Fixed Start Time and what to expect during a live run.

The fixed start time option allows runbook admins to add a date and time to define when a particular task should be actioned by the assigned teams and users within a runbook. It provides greater visibility and control on tasks that are time dependent.

The improved fixed start time is automatically enabled for ALL tasks that have the “add fixed start time” option available in the task detail panel. Tasks with a fixed start time will have the letter “F” followed by the time on the left hand side of the tasks icon.

The “True” fixed start time will only be available during a live run.

Once the tasks’ dependencies have been met (i.e predecessors have been complete) but the fixed start time condition is not yet met, instead of displaying the play icon to indicate the task is ready to start, a clock icon will be shown instead to indicate it is locked. If the assigned teams and users click on the clock icon, a message will appear to instruct users that the tasks can only be started at the given planned date and time.

Runbook admins can override the “True” Fixed Start Time by clicking on the clock icon, the same message will appear but with the additional option to start the task early.

Task start notification will still be sent as soon as the predecessors have been completed, but the notification will inform the assigned users and teams it has a fixed start date and time and to contact your Runbook Admin if required.