Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Execution Order and Node Dependencies

Connections between nodes determine data dependencies and execution order. A node must receive the data it needs before it can complete its work. Canvas position does not define execution order.

Follow the input reference, run the connected nodes, and inspect the completed result.

Before you begin

An editable workflow with connected input, processing, and output nodes.

Key concepts

Term
Definition

Node

A configured processing, input, output, or control step in a workflow. Inspect its inputs and result independently when tracing a problem.

Edge

A connection between workflow nodes. It represents a processing relationship; moving a node on the canvas does not change it.

Dependency

A value or step that another node needs before it can run correctly. Connect the source and map its output to the receiving node.

Branch

One possible path after a routing decision. An unselected branch is not automatically a failed branch.

Output mapping

Selection of a node’s returned field for another step or the final interface. A successful intermediate result is not automatically visible to the end user.

Trace workflow execution

  1. Trace the connections from the workflow input to its output.

  2. Check each processing node for the upstream values it reads.

  3. Run the workflow and inspect node results in dependency order.

The final output comes from the intended processing path.

Behavior and limitations

Independent branches can execute without a guaranteed visual left-to-right order. Routing determines which branch continues. A node result visible from an earlier run does not prove that the node executed in the current run. Check the run record before diagnosing downstream data.

Inputs, Outputs, and Variable References

Last updated

Was this helpful?