Troubleshoot connections and data types

Use the symptom that matches what you see. First identify the two handle labels and the connection kind. A control edge decides whether a node can run; a data edge supplies a typed value. The same visual proximity on the canvas cannot substitute for either connection.

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. For example, starting from a control outcome should not offer Data Source as the next executable step; starting from an RSI numeric output should offer compatible data consumers rather than an Alert control input.

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. Bars → Condition.Left is a common mismatch: Bars is a collection of market bars, while a greater-than comparison needs a number. Calculate RSI with Indicator, or select an appropriate numeric Bar Field, then connect that output to Left.

Try it here

Complete the connections

Recover when a target is unavailable, a connection is rejected, or a node has data but does not run.

Exercise steps

1. Connect the RSI output to the Left input on Condition.
2. Compare data and control connections, then inspect the validation.

Start lesson

A node has data but does not run

First check the node’s behavior. Data Source, Indicator and other data-only nodes have no authorable control input: connect their data to a consumer. If validation reports an obsolete control connection to such a node, remove that connection after inspecting the imported graph. For an executable node such as Condition or Alert, connect a valid control outcome and verify that its upstream branch can occur. In the RSI example, Indicator.RSI → Condition.Left does not evaluate Condition without a control edge from Event Trigger. Conversely, Event Trigger reaching Condition does not create an RSI value without the data path.

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. For Condition, Right is inactive when the right source is Literal or the operator needs only Left. Do not add a second node merely because a generic reference lists Right: inspect the active port and literal setting. If you change the right source to a data port, a compatible Right edge becomes necessary. Validate before saving.