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
  • Assert
  • 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 node reference
  4. /Assert
AdvancedLast verified Sep 30, 2026

Assert

Checks a debug condition and records pass or failure behavior.

On this page
  1. When to use
  2. Example
  3. Check a recorded assumption
  4. Common problems
  5. Next steps

Checks a debug condition and records pass or failure behavior.

When to use

Use it to make an expected invariant visible while examining an eligible debug run.

Example

Assert that a calculated position size is positive before the order path continues in the recorded test.

Try it here

Explore Assert

Checks a debug condition and records pass or failure behavior.

Exercise steps
  1. Inspect the boolean Condition input and the Passed/Failed outcomes.
  2. Compare Skip with Log only for live mode.
Event TriggerConditionIndicatorData SourceAssert
Graph preview — a diagram of the example

Check a recorded assumption

Connect a boolean Condition output to Assert's Condition input in a supported debug or test profile. If the calculated size is positive, the assertion follows Passed; if it is zero or negative, it follows Failed and points to the broken assumption before the order path. Configure the assertion text so the trace says what was expected. The live mode choice can skip or log the check rather than enforcing an automatic safety gate. Do not rely on Assert as a substitute for a real risk or margin branch in an executable strategy.

Common problems

Connect a boolean condition and handle failure as diagnostic evidence. Assert is not a production risk control.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

Node facts

Debug node

These facts come from the current Flow Editor node catalog.

Node type
Assert
Activation role
No activation role
Category
Meta
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Supports debugging
Control inputs
1
Output data types
None

Parameters

NameInput typeRequirementDefaultOptions and constraints
Assertion noteExpressionRequiredNot setNone
Live behaviorSelection listRequiredskipOptions: Skip in live, log only

Primary parameters

  • Assertion note
  • Live behavior

Outcomes

  • Passed
  • Failed

Data inputs

  • ConditionYes or no · Required

Data outputs

None

Related documentation

  • Debug and replay a BacktestInspect an available debug payload in the read-only Replay Dock and follow events, data, variables, and diagnostics.
  • BreakpointMarks a debug pause point for an eligible replay-enabled execution.
  • Log SnapshotCaptures selected graph state for supported debug inspection.

On this page

1 / 5
  1. When to use
  2. Example
  3. Check a recorded assumption
  4. Common problems
  5. Next steps

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

Responsible useGlossary