Navigate to the Task you wish to mark as skipped.  This can be done via Task Detail or the Edit view screen of Runbook - Tasks.

Task can be marked to skip by anyone how has the ability to edit the Runbook.

• A Task cannot be selected to be skipped if it is in an Available,  Active or Completed state
• A Task cannot be skipped if it is in a Suspended state
• Skipped Tasks cannot be Suspended

Skip Task can be applied via the Task Detail screen by checking the Skip Checkbox.

From the Runbook Edit screen select the task that needs to be skipped.  

Either double click into the field of the task you wish to skip in the Skip column or select Edit and then single click into the field required.

A Yes/No selection will be provided for you.

Click Save.

The Duration of a skipped task cannot be updated, while the task is still marked to skip. If the duration of a skipped tasks is to be updated, then the task must be unskipped in the first instance. This can be done from either the Edit Tasks screen, or Task Detail modal window.

When viewing a runbook on the list tasks screen any tasks which have been skipped will have a down arrow placed on top of the task state. An example of this can be shown below.

• Any Tasks which have been marked to skip will still show on the dependency floatover.
• When updating task dependencies skipped tasks will remain to show as potential predecessors.

• Skipped tasks will still be listed for selection as BO Triggers

Skipped tasks will not be treated any differently with regards to critical path logic as they may feature in a chain of dependencies which does contribute to the critical path, therefore skipped tasks may still appear on the Critical Path

If a task is marked to skip but also has trigger comms enabled, communications for this tasks will not be sent.