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. /Backtests and responsible use
All levelsLast verified Aug 23, 2026

Backtests and responsible use

Interpret simulated results with appropriate limits and avoid treating them as predictions or advice.

On this page
  1. What a Backtest can show
  2. What it cannot show
  3. Use results responsibly

The Flow Editor helps express strategy rules. A Backtest evaluates those rules under a historical simulation.

What a Backtest can show

A Backtest can show how the saved graph behaved for the selected period, data, starting capital, execution model, costs, and other configured assumptions. It can help compare changes and find unexpected paths.

What it cannot show

A Backtest does not predict future results and does not guarantee that an order could be executed under live conditions. Historical data can be incomplete or corrected. Liquidity, latency, slippage, fees, market impact, corporate actions, and operational failures can differ from the simulation.

Debug and replay explain recorded simulated behavior; they do not increase its predictive value.

Use results responsibly

  • Review the complete configuration and costs.
  • Test different periods and adverse assumptions.
  • Investigate unusually strong or stable results.
  • Keep validation, risk branches, and failure outcomes explicit.
  • Treat examples as learning material, not recommendations.
  • Make your own decisions and seek qualified advice when appropriate.

Nothing in the product documentation is investment, legal, tax, or financial advice.

Related documentation

  • Run a BacktestSave a ready graph, review Backtest inputs and costs, then submit the simulation.
  • Debug and replay a BacktestInspect an available debug payload in the read-only Replay Dock and follow events, data, variables, and diagnostics.
  • Flow Editor examplesStudy small, valid strategy patterns and adapt them to your own requirements.

On this page

1 / 3
  1. What a Backtest can show
  2. What it cannot show
  3. Use results responsibly

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

Responsible useGlossary