Validation

The Validate button on the General tab checks a machine for common configuration problems and reports what it finds as a notification. It never changes anything — it only tells you what to look at.

What it checks

Missing initial state

Every machine should have exactly one initial state — the status an entity starts in. If none is set, entities have no defined starting point.

Fix: set an initial state from the States tab or the Initial state field on the General tab. See Managing states.

Orphaned states

A state with no transitions at all — nothing leads to it and nothing leads out. It can never be entered or left, so it serves no purpose in the flow.

Fix: add the transitions that connect it, or remove the state if it is not needed.

Unreachable states

A state that has no incoming transition. The flow can never arrive at it (unless it is the initial state), so entities will never reach that status.

Fix: add a transition that leads into it, or make it the initial state if that was the intent.

Duplicate transitions

Two transitions with the same action, source and target. The duplicate has no effect and only clutters the machine.

Fix: delete the redundant transition from the Transitions tab. The add form already blocks creating exact duplicates, so this mainly catches ones imported or created before that check.

When to run it

After building a new machine, before relying on it.
After adding or removing states or transitions on any machine.
After editing a core state machine, as a safety check.

A clean result confirms the machine has a starting point, no dead ends and no redundant transitions.