> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/workflow-execution/execution-order-and-node-dependencies.md).

# 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.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FbD3Xura92Kb1RjSj8Bhr%2Fexecution-order-and-node-dependencies.mp4?alt=media&token=f8cd54dd-fd00-44f4-a885-74a07ceef2f5>" %}
Follow the input reference, run the connected nodes, and inspect the completed result.
{% endembed %}

## 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.

## Related resources

[Inputs, Outputs, and Variable References](https://docs.stackai.com/technical-reference/workflow-execution/inputs-outputs-and-variable-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/workflow-execution/execution-order-and-node-dependencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
