Skip to main content

Find out why tasks are stuck between stages

When tasks sit in a stage and don't reach the next one, the step between the two stages says why.

Who can do this: any member who can see the project's tasks. Acting on the reason, such as approving, needs what the project's pipeline asks for that step.

  1. In the sidebar, select Tasks, then the project. If the board lists every task by state, select Pipeline at the top. The stage strip sits under the top line: one block per stage, such as Ideas, Building, Dev and Production.
  2. Find the step after the stage your tasks are in. Between two blocks, an icon marks the step: Start, Merge, Start and merge, Move or Release. Hover it for its name.
  3. Read the coins after the step's icon. A red coin counts the tasks that failed at the step and a grey coin the tasks it holds. Hover a coin for its words, such as 2 failed or 3 waiting. While the merge lane works, the Merge icon turns, with the count in flight on it.
  4. Hover the chip at the end of the step, such as 1/2 approvals, Frozen, Soak 42m, Off hours, In line or Sign-off. On a phone, tap it, and tap it again to close it. It names the first thing that holds the step; the list that opens gives every reason, one per line, such as Frozen until Fri 18:00 or Ready in 42m.
  5. Select the grey coin. The list under the strip shows only the tasks the step holds, under Waiting on and the same chip.
  6. Select the red coin instead to list the tasks that failed at the step. Select one to open it beside the list and read why it failed.
  7. Act on the reason the chip gave:
  8. Select the stage's block to see all its tasks again.

Once nothing holds the step, the held tasks move on by themselves, or wait for someone to press the step, as in Move tasks to the next stage. Every reason a step can give is listed in Release to production.