Task Lateness

Setting the Task Late Threshold

The Deployment Manager can set a ‘lateness’ threshold for each Runbook. The ICEFLO default setting is 5 minutes but can be easily changed  at any time  via the Runbook Details Panel.

A task is considered to be late in any of the following three scenarios (the default this is set to 5mins):

  1. Been ‘AVAILABLE’ for longer than 5 mins
  2. Still ‘ACTIVE’ over 5 mins beyond the planned Duration
  3. Still ‘SUSPENDED’ for over 5 mins beyond the Estimated Resolution Time of the corresponding issue
Task Lateness

Identifing Late Tasks

Tasks can be identified as being late via a few methods on the List Tasks Screen:

Task Status Visual - This example highlights tasks which have been late in starting and tasks which have been late in completing.

You could also chose to filter in on the Late Column which is present on the list tasks screen

List Tasks Screen

The Inflight Tasks panel also highlights tasks which are identified as being late.

RTUP

Clicking on the Late visualisation on the In Flight Tasks panel will filter your Tasks List to only Late Tasks.

The Runbook must be in a state of Active for this panel to present.