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 guides
  4. /Reset a Flow safely
IntermediateLast verified Sep 30, 2026

Reset a Flow safely

Return to the mode's default trigger while checking the backup, confirmation and recovery path.

On this page
  1. Before you reset
  2. Run the two-step confirmation
  3. Recover or investigate

Result: the canvas contains only the default primary trigger for its existing mode. Tactical returns to Event Trigger; Portfolio returns to Schedule Trigger. The mode and strategy identity do not change. Reset removes the current nodes and connections from the working graph, so use it only when you intend to rebuild that graph.

Before you reset

Open the strategy you mean to change and check its name and mode. Save the current graph and wait for a success state. For a durable named point to return to, create a checkpoint and verify that it appears in version history. A save still in progress, an offline state or a conflict is not evidence of a backup. Resolve those states before proceeding.

The Reset flow dialog explains the backup available for this action. The editor keeps a pre-reset graph in local Undo history. When a server save is available, it also makes a manual save before applying reset; if that save fails, reset is blocked. Undo history is local to the editing session, so do not rely on it as a long-term copy or close the tab before checking a server-side version.

Run the two-step confirmation

  1. Choose Reset flow in the toolbar or editor command palette. If the action is unavailable, first change the graph; the already-default graph has nothing to reset.
  2. Read the first confirmation step. Cancel here if you are viewing the wrong strategy or your prior save is unresolved.
  3. Continue to the final confirmation and choose Create backup and reset. Wait for the action to finish. Do not reload the page to force it through.
  4. Confirm that only Event Trigger (Tactical) or Schedule Trigger (Portfolio) remains and no edges remain. Validation may report that the new minimal graph is not yet ready for a Backtest; reset is a starting point, not a complete strategy.
  5. Save the new graph and wait for confirmation if you intend to keep the reset state.
Try it here

Practice a Flow reset

Return to the mode's default trigger while checking the backup, confirmation and recovery path.

Exercise steps
  1. Open Reset Flow and review both confirmation steps.
  2. Inspect the remaining primary and restore the exercise’s pre-reset snapshot.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

Recover or investigate

Immediately after reset, Undo can restore the pre-reset graph in the current session. If you need to recover later, open the saved version or checkpoint and inspect it in read-only mode before choosing Restore. Restoring creates a new current version; it does not rewrite the historic one. If the reset was blocked, read the save or conflict message and follow save and conflict recovery; do not repeat confirmation until the backup state is clear.

Check: you can name the strategy, its mode, the pre-reset saved version and the current one-trigger graph. If you cannot identify the saved version, stop before leaving the editor.

Related documentation

  • Create checkpoints and restore versionsCreate a named recovery point, preview history safely, and restore without deleting older versions.
  • Save and resolve conflictsProtect local edits, recover from offline or error states, and choose the correct version after a conflict.
  • Saves, versions, and checkpointsUnderstand dirty state, autosave, conflicts, history, and non-destructive restore.

On this page

1 / 3
  1. Before you reset
  2. Run the two-step confirmation
  3. Recover or investigate

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

Responsible useGlossary