Validation and readiness
Distinguish blocking errors from guidance and make a graph ready before testing it.
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.
Select an issue to focus the relevant node or area when that action is available.
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.
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.
Use Fix validation issues for a repeatable recovery process.
Related documentation
- Fix validation issuesUse the validation area to locate a blocking problem, correct it, and confirm that it is resolved.
- Troubleshoot activation and validationRecover from a missing primary trigger, duplicate activation attempt, cycle, or incomplete required setting.
- Run a BacktestSave a ready graph, review Backtest inputs and costs, then submit the simulation.