Validation and readiness

Validation checks whether the graph can be interpreted safely enough for the next action.

Blocking issues

A blocking issue prevents the graph from being ready. Common causes include a missing primary activation, an incomplete required parameter, an incompatible or missing connection, or a path that forms a cycle.

Read the location and consequence together. A blank Tactical graph needs a primary Event Trigger; a blank Portfolio graph needs the appropriate scheduled primary activation. A Condition whose Left input has no compatible numeric value cannot make the intended RSI comparison even if its Greater-than operator and literal threshold are filled in. Adding a control edge to the Condition does not replace that data input.

Select an issue to focus the relevant node or area when that action is available.

Try it here

Repair the example

Distinguish blocking errors from guidance and make a graph ready before testing it.

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

Warnings and guidance

A warning deserves review but may not block every operation. Read the message and recovery action instead of treating every item as the same severity.

For example, the RSI Starter's unconnected No Match outcome can appear as informational guidance while Match → Alert remains connected. You may leave the intentional branch unused or disable that outcome in the Inspector. By contrast, a broken required connection should be repaired before relying on a run. Read the actual severity and node context; the number of messages alone is not a readiness verdict.

A locked feature is an availability state, not a validation issue.

When to validate

Validate after adding a branch, changing parameters that affect ports, restoring a version, or before opening the Backtest flow. Saving stores your current graph; it does not turn an invalid graph into a ready one.

There are three separate checkpoints: configured means the node has the intended settings; valid means the graph passes the relevant structural checks; saved means a version has been persisted. A Backtest additionally depends on plan, data, and run configuration. A valid saved graph can therefore still be unable to submit a particular simulation. Resolve the reason shown at that step rather than altering a sound graph to make a disabled action clickable.

Use Fix validation issues for a repeatable recovery process.