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
  • Breakpoint
  • 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. /Breakpoint
AdvancedLast verified Sep 30, 2026

Breakpoint

Marks a debug pause point for an eligible replay-enabled execution.

On this page
  1. When to use
  2. Example
  3. Inspect before an action
  4. Common problems
  5. Next steps

Marks a debug pause point for an eligible replay-enabled execution.

When to use

Use it while investigating the order or timing of control paths in a supported debug run.

Example

Place a Breakpoint before Order to inspect the recorded values immediately before submission.

Try it here

Explore Breakpoint

Marks a debug pause point for an eligible replay-enabled execution.

Exercise steps
  1. Edit the breakpoint label and inspect its Next outcome.
  2. Follow the connected activation; stopping on a breakpoint belongs to debug replay.
Event TriggerBreakpoint
Graph preview — a diagram of the example

Inspect before an action

Place Breakpoint on the control path before Order and give it a label such as Before submission. In a supported recorded debug or replay workflow, inspect the values present at that point, then compare them with the subsequent Order outcome. Its Next branch keeps the graph's intended path visible. A Breakpoint on the canvas does not by itself pause a live browser or exchange order, and it is not a guarantee that every Backtest profile offers interactive stepping. Check the available debug controls for the selected run.

Common problems

It affects debug behavior only when the run records the required data. It does not pause normal editing or make replay available.

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
Breakpoint
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
Debug labelTextOptionalNot setNone

Primary parameters

  • Debug label

Outcomes

  • Next

Data inputs

None

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.
  • Troubleshoot Backtests and replayRecover from blocked Backtest launch, preview or submission errors, and unavailable full replay.
  • Log SnapshotCaptures selected graph state for supported debug inspection.

On this page

1 / 5
  1. When to use
  2. Example
  3. Inspect before an action
  4. Common problems
  5. Next steps

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

Responsible useGlossary