Troubleshoot connections and data types
Recover when a target is unavailable, a connection is rejected, or a node has data but does not run.
Use the symptom that matches what you see.
A target is not offered
Confirm whether you started from a control or data handle. Open Data Ports and verify that the source output is active. Then check the expected target type, strategy mode, and plan availability.
Quick add intentionally hides incompatible candidates.
A connection is rejected
Check source and target direction, handle type, and data type. Remove any connection that would create a cycle. If the value is structured and the target expects a scalar, add the corresponding Field node.
A node has data but does not run
Data does not continue execution. Connect a valid control outcome to the node’s control input. Then confirm that the upstream outcome can actually occur.
A port disappeared
A parameter change can alter active ports. Reopen the node’s Parameters and Data Ports, correct the configuration, and reconnect the intended value. Validate before saving.
Related documentation
- Control and data connectionsUse control connections to continue execution and data connections to pass compatible values.
- 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.