Home > Workflows > Workflow Nodes > Node States
At any time, a node has a state that indicates its status. The state of the node is one of the following:
Invalid: The node has not been completely defined and cannot run as is.
Most nodes must be connected to be valid, that is, must have the input defined. A Data node does not need to be connected to be valid.
Error: The node attempted to run but encountered an error. For nodes that perform several tasks such as build several models, any single failure sets the status of the node to Error.
You must correct all problems to clear the Error state.
Any change clears the Error state to Ready, if the problem is a server runtime failure not attributable to standard specification validations. To find out if the problem is really fixed, run the node.
Ready: The node is properly defined but has not yet run and is not invalid.
Nodes that are Ready are sometimes said to be Valid.
Running: The node is running. A running node is locked; it can be viewed, but it cannot be edited.
Queued: The node is part of a run chain but is not yet running.
In complex nodes, such as build nodes, a build step is running but another step may be queued.
Complete: The node ran successfully.
Stale: The node is not up-to-date; for example, the data has changed.
A node is Stale if the node has already been run and completed, but there is a request to rerun it, or if a parent node has changed.
Wait: The node is waiting to run; it cannot be edited.
Warning: The node ran but did not generate all expected results, such as an Association Build that did not generate rules.
The state of the node may be shown graphically. For example, red border on a node indicates that is not valid; a green check mark indicates that the node is Complete.
For more information about the state, float the cursor over the node.