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
All levelsLast verified Sep 30, 2026

Flow Editor concepts

Understand the rules that make a Flow graph valid and ready to test.

On this page
  1. Strategy design
  2. Readiness and lifecycle
  3. Reading order

These pages explain why the editor accepts some graphs and rejects others. If you are new, read them in the order below and then try the corresponding action in the RSI quickstart. If you already build strategies, jump to the rule you need to verify.

Strategy design

  1. Tactical and Portfolio strategies explains the two modes and why their primary triggers and available nodes differ.
  2. How a strategy starts and continues explains the primary activation, control outcomes, waits and why canvas placement is not execution order.
  3. Nodes, parameters, outcomes and ports names the pieces you see in the canvas and Inspector.
  4. Control and data connections explains the two networks in one graph and how types constrain an edge.

For example, Event Trigger can send control to Condition while Indicator supplies an RSI data value to its Left input. Both are needed for a decision. Condition.Match is a control outcome; Condition.Result is a Boolean data output. This distinction matters more than where the nodes sit on screen.

Readiness and lifecycle

  • Validation and readiness separates graph errors, warnings and information from Backtest data and plan prechecks. A graph can be saved without being ready to run.
  • Saves, versions and checkpoints explains local edits, confirmed saves, read-only history and non-destructive restore.
  • Plans and feature availability explains why a node, an option, a Backtest feature or a Quant Hub metric can be visible yet unavailable to the current account.

Reading order

For a first strategy, read modes → activation → node anatomy → connections → validation → saves, then use the guides to make the change. For an existing graph, start at the failing point: connection troubleshooting, activation troubleshooting, or save recovery. The glossary provides short definitions.

Related documentation

  • Get started with the Flow EditorUnderstand strategy modes, workspace areas, validation, and the save lifecycle before building.
  • Flow Editor guidesComplete a specific Flow Editor task with direct, verifiable steps.
  • Flow Editor node referenceBrowse every node currently available to add, with generated facts and practical guidance.

On this page

1 / 3
  1. Strategy design
  2. Readiness and lifecycle
  3. Reading order

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

Responsible useGlossary