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

Flow Editor documentation

Create, connect, validate, save, and test visual trading strategies.

On this page
  1. Start here
  2. Choose a route
  3. Complete a task
  4. Understand the model
  5. Browse and troubleshoot

Flow Editor is the workspace for designing a strategy as a graph of nodes and connections. A node can start an evaluation, provide data, decide or act. A control connection answers what can run next; a data connection answers which value is needed. Drawing a graph, saving it and running a Backtest are different steps. Keep these articles open while you work.

Start here

  1. Read Getting started to locate the canvas, palette, Inspector, validation and save state. Choose Tactical for supported market events or Portfolio for scheduled allocation; the mode stays fixed after creation.
  2. Follow Build an RSI Momentum Alert. You will create a Starter copy, identify five nodes, change a threshold, validate, save and confirm the saved result after reopening.
  3. Use Create a strategy when you want a different available Starter or a blank graph.

The RSI exercise needs no trading experience. A bar summarizes market data over one interval; RSI is a numerical indicator calculated from bars. The glossary explains those and the editor terms as you encounter them.

Choose a route

You want to…Start withThen use
Learn the editor for the first timeGetting startedRSI quickstart
Find why a graph does not executeActivation and flowControl and data connections
Build a Tactical order pathTactical modeOrder lifecycle example
Build a Portfolio allocationPortfolio modePortfolio rebalance example
Check a field, port or plan requirementNode referencePlans and availability

Complete a task

The guides follow actions in the editor. For a typical change, configure a node, connect its active ports, fix validation issues, then save and verify the result. Before experimenting, create a checkpoint. Reset flow has its own backup and recovery procedure.

A saved strategy is not automatically tested. Run a Backtest from a ready graph, then inspect runs and results in Backtest Center.

Understand the model

Start with nodes, parameters, outcomes and ports. In the RSI example, Event Trigger reaches Condition through control, while Indicator supplies the RSI number to Condition through data. Condition.Match can reach Alert; its Boolean Result is a different, data output. Canvas position alone sets no execution order. The concepts explain modes, activations, validation, versions and availability; the examples show how the rules combine.

Browse and troubleshoot

Search the node reference when an Inspector field or port is unclear. A reference lists possible configurations; a conditional field or port appears only when its setting makes it active. If a connection fails, an action is locked or a run lacks the expected event, choose the matching symptom in Troubleshooting.

Backtests are simulations under their data and cost assumptions. Read Backtests and responsible use before interpreting results as evidence about a strategy.

Related documentation

  • Get started with the Flow EditorUnderstand strategy modes, workspace areas, validation, and the save lifecycle before building.
  • Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.
  • Flow Editor node referenceBrowse every node currently available to add, with generated facts and practical guidance.

On this page

1 / 5
  1. Start here
  2. Choose a route
  3. Complete a task
  4. Understand the model
  5. Browse and troubleshoot

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

Responsible useGlossary