Fix validation issues

Correct one blocking issue at a time and validate again after each structural change.

Locate the issue

Open the validation area and read the complete message. Use its action to focus the affected node or graph area when available. Distinguish an error from a warning or plan lock.

Apply the recovery

• For a missing activation, add the correct primary trigger for the strategy mode.
• For a required parameter, select the node and complete the named setting.
• For an incompatible value, inspect both Data Ports and reconnect compatible types.
• For a disconnected control path, connect the relevant outcome to the next node.
• For a cycle, remove the connection that returns to an earlier path.

Do not change unrelated nodes simply to clear the count.

Example: an RSI value is missing

Suppose Event Trigger reaches Condition through a control connection and Condition has Greater than 60, but its Left data input is empty. The activation path exists; the comparison value does not. Select Condition from the issue, inspect Data Ports, and connect the numeric RSI output of Indicator to Left. Confirm that Indicator receives bars from Data Source. If the editor rejects the edge, inspect the source and destination types and the current Condition settings. Do not connect bars directly to a numeric Left input or add another Event Trigger to compensate.

If you changed Condition from Right port to Literal, check whether the old Right connection is still relevant. Keep one intended source of the comparison value and use the Inspector's active-port view to correct the graph. The connection guide explains the two edge kinds.

Try it here

Repair the example

Use the validation area to locate a blocking problem, correct it, and confirm that it is resolved.

Exercise steps

1. Select the missing-input diagnostic and find its node.
2. Connect RSI to Left; verify that the blocking issue disappears.

Start lesson

Confirm readiness

Run validation again. Confirm that the original item is gone and that the change did not create another blocking issue. Save the corrected graph before launching a Backtest or leaving the editor.

If the remaining item is an Info about the intentionally unused No Match branch, decide whether to leave it as a documented branch or disable that outcome. If submission is still unavailable after graph validation, inspect the Backtest dialog's plan, data and configuration requirements; those are separate from a missing edge. When a save reports offline or conflict, use save recovery before closing the editor.