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 guides
  4. /Fix validation issues
BeginnerLast verified Sep 30, 2026

Fix validation issues

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

First strategy · Step 8 of 10

On this page
  1. Locate the issue
  2. Apply the recovery
    1. Example: an RSI value is missing
  3. Confirm readiness

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

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.

Related documentation

  • Validation and readinessDistinguish blocking errors from guidance and make a graph ready before testing it.
  • Troubleshoot activation and validationRecover from a missing primary trigger, duplicate activation attempt, cycle, or incomplete required setting.
  • Troubleshoot connections and data typesRecover when a target is unavailable, a connection is rejected, or a node has data but does not run.
PreviousConfigure a nodeNextSaves, versions, and checkpoints

On this page

1 / 4
  1. Locate the issue
  2. Apply the recovery
    1. Example: an RSI value is missing
  3. Confirm readiness

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

Responsible useGlossary