Control and data connections
Use control connections to continue execution and data connections to pass compatible values.
The Flow Editor uses two connection kinds. They answer different questions.
Control connections
A control connection answers: what can run next? It joins an outcome on one node to the control input of another node.
Control connections carry no market value. Their meaning comes from the source outcome, such as Match, Submitted, or After Delay.
Data connections
A data connection answers: which value should this input use? It joins a typed output to a compatible typed input.
Data connections do not execute their target. A node that needs to run also needs a valid control path unless it is a value source used by another node.
Compatibility
The editor offers only compatible targets when you start from a handle. If a seemingly relevant node is absent, confirm the connection kind, data type, mode, plan availability, and current node configuration.
The graph cannot contain cycles. Use validation after rewiring a branch.
Related documentation
- Connect nodesCreate a compatible control or data connection and verify the resulting path.
- Use Quick addAdd a compatible next node from a handle or the selected node without searching the full palette.
- Troubleshoot connections and data typesRecover when a target is unavailable, a connection is rejected, or a node has data but does not run.