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

Log Snapshot

Captures selected graph state for supported debug inspection.

On this page
  1. When to use
  2. Example
  3. Capture the value behind a branch
  4. Common problems
  5. Next steps

Captures selected graph state for supported debug inspection.

When to use

Use it when replay should expose a value at a meaningful point in the control path.

Example

Capture a calculated indicator value immediately before Condition evaluates.

Try it here

Explore Log Snapshot

Captures selected graph state for supported debug inspection.

Exercise steps
  1. Change the label and the Include variables option.
  2. Inspect the optional Value input and the Next control outcome.
Event TriggerLog Snapshot
Graph preview — a diagram of the example

Capture the value behind a branch

Place Log Snapshot on a recorded debug path before the decision you are investigating. Set a meaningful label such as RSI before threshold and connect the numeric RSI value to Value. In a run where the value is 58, the snapshot can explain why Greater-than-60 took No Match. Enable variable capture only when those variables are relevant; it increases the amount of recorded context and should not be used to expose secrets. Log Snapshot's Next control continuation is distinct from its data input, and a snapshot is diagnostic evidence, not an execution result.

Common problems

Only recorded debug runs can show the snapshot. Avoid capturing sensitive values and do not treat logging as validation.

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
Log Snapshot
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
Snapshot labelTextRequiredNot setNone
Include variablesYes or noOptionaltrueNone

Primary parameters

  • Snapshot label

Outcomes

  • Next

Data inputs

  • Valueany · Optional

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.
  • AssertChecks a debug condition and records pass or failure behavior.

On this page

1 / 5
  1. When to use
  2. Example
  3. Capture the value behind a branch
  4. Common problems
  5. Next steps

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

Responsible useGlossary