Join / Data Merge
Converges control branches as a Join or combines compatible data inputs as a Data Merge.
Converges control branches as a Join or combines compatible data inputs as a Data Merge.
When to use
Use Join when forward control branches must converge; use Data Merge when homogeneous data values need one combined output.
Example
Join two completed control branches before one Alert, or merge compatible data inputs for a downstream consumer.
Choose the right kind of merge
In Join role, bring two control branches into the node and continue from Merged after the configured join behavior. This answers “when may execution continue?” In Data Merge role, connect compatible data values to Inputs and consume the Merged Data collection. This answers “what values are grouped?” A Data Merge does not replace an Event Trigger, and a Join does not turn two unlike values into a single number. Choose Role before wiring ports, then inspect the active control and data connections because changing Role changes the meaning of the node.
Common problems
Choose the intended Role (Join or Data Merge) and connect homogeneous inputs. It cannot make incompatible types or graph cycles valid.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.
Related documentation
- GateCombines control arrivals according to a configured pass rule.
- Control and data connectionsUse control connections to continue execution and data connections to pass compatible values.
- Troubleshoot connections and data typesRecover when a target is unavailable, a connection is rejected, or a node has data but does not run.