Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor concepts
  4. /Validation and readiness
BeginnerLast verified Sep 30, 2026

Validation and readiness

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

On this page
  1. Blocking issues
  2. Warnings and guidance
  3. When to validate

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.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

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.

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.

On this page

1 / 3
  1. Blocking issues
  2. Warnings and guidance
  3. When to validate

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary