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 mode guides
  4. /Build Tactical strategies
IntermediateLast verified Sep 30, 2026

Build Tactical strategies

Design an event-driven graph with one primary trigger, explicit control branches, and typed market data.

Advanced Tactical · Step 1 of 2

On this page
  1. Start the graph
  2. Build the decision path
  3. Add effects carefully
  4. Verify

Tactical strategies respond to supported market events for an instrument.

Start with an alert-only graph if you are new to trading. It teaches activation, a market-data dependency, a decision, and an observable Backtest event without introducing an order. A saved strategy is editable work; it does not trade or send live notifications by itself.

Start the graph

Use one primary Event Trigger. Choose the event and instrument settings that match the downstream data. A separate Data Source can provide bar history to indicators without becoming another activation.

For a one-minute bar-close example, keep the Event Trigger symbol and timeframe aligned with the Data Source used by Indicator. An RSI period of 14 means the calculation needs historical bars; it does not mean the strategy is evaluated only every 14 minutes. Data coverage and the Backtest window still determine whether an evaluation has the data it needs.

Build the decision path

Connect control from Event Trigger to Condition, Gate, or another node that can run next. Feed typed values through data connections. A Condition needs both a control arrival and the values it compares.

In the RSI Starter, follow two routes separately:

RouteConnectionPurpose
ControlEvent Trigger → Condition → Alert on MatchDecides when Alert can run.
DataData Source → Indicator → Condition.LeftSupplies RSI for the comparison.
ParameterCondition.Right literal = 60Supplies the fixed threshold without a Right data edge.

With RSI 58 the Match branch is not selected; with RSI 62 it is. The > operator checks the level on each evaluation, so it can match repeatedly while RSI remains above 60. This is not a crossing signal. To change the signal, change the operator or graph deliberately rather than merely changing the Alert message.

Try it here

Follow an order lifecycle

Design an event-driven graph with one primary trigger, explicit control branches, and typed market data.

Exercise steps
  1. Inspect Order and Await Order Event, including their different outcomes.
  2. Trace submitted to the wait node; inspect filled, rejected and timeout without placing an order.
Event TriggerOrderAwait Order Event
Graph preview — a diagram of the example

Add effects carefully

Alert is a low-complexity first effect. Trading paths can include Position Sizer, Margin Check, Order, Await Order Event, Position Monitor, Cancel Orders, and leverage monitoring when available. Connect failure and risk outcomes instead of leaving important branches unexplained.

For a trading path, distinguish three events: Order submits a request and reports its immediate submission outcome; Await Order Event can resume when a later lifecycle outcome such as a fill is recorded; Position Monitor follows a valid filled path. An Order.Submitted outcome is not proof of a fill. Before connecting a node that depends on a position, trace the filled lifecycle path and the matching ticket/value data. The Tactical order example develops this pattern.

Verify

Resolve validation issues, save, create a checkpoint before a large change, and run a Backtest only after reviewing its configuration and costs.

Check the result against your stated goal: a valid alert-only graph can produce no alerts if the condition never matches in the selected period. A graph with an Alert and no Order cannot produce a trade. If a trading branch is unobserved, inspect the selected outcome, the data reaching that node, and the Backtest's recorded events before changing the strategy.

Related documentation

  • How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
  • Tactical order and position monitoringUnderstand a Tactical pattern that sizes an order, checks margin, tracks its lifecycle, and monitors the position.
  • Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.
NextTactical order and position monitoring

On this page

1 / 4
  1. Start the graph
  2. Build the decision path
  3. Add effects carefully
  4. Verify

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

Responsible useGlossary