not_started.
The placement rule
Current customer handover state comes first. If Fleet Manager reports a device asavailable or in_use, the board places it at the end of its pipeline with succeeded:
release for customer hosts, or enrolment for hypervisors whose pipeline ends there. Job
history does not move a currently customer-ready device back to an earlier column.
available or in_use, placement follows the newest attempt
that was not cancelled, terminated, or superseded:
A device cannot skip an earlier stage that never completed successfully. This is the
prefix clamp: for example, a later single-node attempt cannot place a device past a failed
enrolment. The clamp does not apply while current
operational_status already proves the device
is available or in_use.
concurrent_workflow_running suppression reason alongside no_next_stage, even though current
customer-ready state keeps its placement green.
The board is recalculated on every refresh; there is no stored pipeline column to backfill. Use it
for orientation, not as the only proof for a diagnosis or as an unchecked bulk-action list.
For raw Job states, see Status Reference. For exact device-specific
pipelines, placement ordering, acceptance-gate rules, customer-ready overrides, and the prefix
clamp, see Device State Machines.