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 troubleshooting
  4. /Troubleshoot activation and validation
BeginnerLast verified Sep 30, 2026

Troubleshoot activation and validation

Recover from a missing primary trigger, duplicate activation attempt, cycle, or incomplete required setting.

On this page
  1. Primary activation is missing
  2. A trigger was replaced
  3. The graph contains a cycle
  4. A required setting is incomplete

A ready graph has exactly one primary activation that matches its permanent mode. Start with the specific validation issue, select it to focus the affected node or edge when available, and fix that cause. A zero-error count alone does not guarantee that a chosen historical period will produce an Alert or trade.

Primary activation is missing

An ordinary new strategy already contains its primary. If an imported or damaged graph reports none, identify its mode first: Tactical requires Event Trigger and Portfolio requires Schedule Trigger. Add the appropriate primary if the editor offers that repair, configure it, and reconnect the intended control path. Safety Trigger cannot resolve a missing Portfolio primary because it is an auxiliary guard. If the editor cannot repair the imported graph, preserve the current version and review Reset a Flow safely before starting again; reset removes the working nodes and edges.

Try it here

Repair a missing primary activation

Find the missing primary in validation and add a compatible activation to the graph.

Exercise steps
  1. Read the blocking activation diagnostic. Open Add node and add Event Trigger.
  2. Reconnect fired to Condition and inspect the remaining validation messages.
Data SourceIndicatorConditionAlert
Graph preview — a diagram of the example

A trigger was replaced

A primary changes only through the explicit Replace primary action. Adding or pasting a second primary is disabled, and the last one cannot be deleted in an ordinary editable graph. If you replaced it unintentionally, use Undo while the edit is still in the current session. Otherwise configure the replacement and trace every outgoing control edge again; replacement does not prove downstream event settings still match.

The graph contains a cycle

Follow the highlighted edge from source to target and find where the path returns to an earlier executable node. Remove that return edge, then rebuild the behavior as a forward path. Delay does not make a control cycle valid. If you intended to wait for another event, use a supported continuation such as Delay or Await Order Event on a valid forward path; neither starts a new primary.

A required setting is incomplete

Select the referenced node and open Parameters. Complete the field named by the diagnostic, including any dependent control revealed by an earlier choice. For example, Condition with a literal right source uses its literal value, while a port source requires a compatible Right edge. Then review Data Ports: changing parameters can reveal or hide a port and leave an existing connection inactive. Validate again, save only after the graph is ready for the intended action, and use connection troubleshooting if a handle still refuses the edge.

Related documentation

  • How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
  • Fix validation issuesUse the validation area to locate a blocking problem, correct it, and confirm that it is resolved.
  • Validation and readinessDistinguish blocking errors from guidance and make a graph ready before testing it.

On this page

1 / 4
  1. Primary activation is missing
  2. A trigger was replaced
  3. The graph contains a cycle
  4. A required setting is incomplete

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

Responsible useGlossary