An execution that found no work

A task that works items such as issues may fire when nothing is left for it to take. Its execution then ends as No work. That is a normal result, not a failure: the dashboard shows it apart from a failed execution wherever it lists executions, and it is never listed among the executions that need your attention.

The queue

The Execution queue panel of the Executions screen lists the work items waiting for a later cycle, marked To resume or To retry. It leaves out the ones already finished: a work item that was completed or closed is not listed. An execution that found no work adds nothing to the queue. The queue panel's statuses explains what each status means and which items appear under it.

The recent history

Beside the queue, the Recent history panel lists the latest executions that ended, each with a mark of its result. Selecting one opens it, and See all opens the History screen.

• No work. An execution that found no work has a circle in a neutral tone, labelled No work.
• Failed. A failed execution keeps its own mark, a cross in the tone of an error, labelled Failed.

The two never share a mark or a label, so an execution that did nothing never reads as one that went wrong.

Needs your attention

The Needs your attention panel of the Overview lists the recent executions that failed, that need attention, or that were interrupted. An execution that found no work is not listed there: nothing went wrong in it.

The History screen

The History screen lists every execution with its status, shown with an icon and its name: an execution that found no work reads No work in the same neutral tone, and a failed one reads Failed in the same tone of an error. Its Status filter offers No work, so you can list those executions alone.