Node State
Lifecycle / status state for every Krill node.
Consumed widely: the UI colours node chips by this value, processors gate work on it (e.g., PAUSED suppresses execution), the SSE layer emits changes as STATE_CHANGE events, and downstream logic (triggers, filters) reacts to specific transitions.
Both enum names and ordinals are part of the public wire contract and are observed by clients across JVM, Android, iOS, and wasmJs — do not rename or reorder without a coordinated migration.
Use isInvokable to check whether a node in this state may receive a deliberate invocation (via krill.zone.shared.node.NodeHttp.invokeNode).
Entries
The node is actively executing its work (reading a sensor, firing an executor, etc.).
The node was just created; shown briefly to allow the UI to fade it in, or it changed in a way where it needs to be completely refreshed
The user has submitted edits; the node will transition away once the server acknowledges.
A snapshot (historical time-series payload) arrived for this node; used to invalidate cached views on the client side so the next read pulls fresh data.
The caller lacks authorisation to view or mutate this node (missing/invalid API key).
The node was reset to its initial / cleared state by a krill.zone.shared.node.NodeAction.RESET action; parallel to EXECUTED for the reset execution path.