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 save, offline, and conflicts
IntermediateLast verified Sep 30, 2026

Troubleshoot save, offline, and conflicts

Protect local edits and recover when the editor cannot confirm the latest saved version.

On this page
  1. The editor is offline
  2. Save failed
  3. A conflict appeared
  4. An older version is needed

Do not close the editor while it cannot confirm the latest saved version. The visible Saved state is the check that your most recent change reached storage; a button click or autosave attempt alone is not confirmation.

The editor is offline

Keep the tab open and restore the connection. Use the offered retry action or Save strategy after connectivity returns. Wait for Saved before navigating away. If the network returns but the state remains Offline, read the specific error and avoid opening a second editable tab of the same strategy while local edits are unresolved.

Save failed

Read the error and retry only after addressing its cause. A validation or permission problem requires a different correction than a temporary network failure. If the failure continues, preserve the open tab and avoid making the same strategy editable in another tab. Do not refresh merely to clear the message: a refresh can discard local work that has not been accepted.

A conflict appeared

Another accepted version changed during your edit. Compare your intended graph with the accepted server version before choosing Keep my changes or Reload server version. The latter replaces the conflicting local graph. Repeatedly pressing Save cannot overwrite the conflict safely; choose a resolution deliberately.

After resolution, validate, save, and reopen the same strategy to confirm the accepted result. If you intended to preserve your local edits but the reopened graph differs, check that you opened the current version and inspect version history before making more changes.

Try it here

Practice a save conflict

Protect local edits and recover when the editor cannot confirm the latest saved version.

Exercise steps
  1. Change the threshold on Condition, then save a local checkpoint.
  2. Choose a simulated save outcome. Recovery actions appear when that state requires them.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

An older version is needed

Open history and preview the candidate in read-only mode. To restore it, go to the strategy detail page's Versions tab and choose Restore on the eligible entry. The historical editor preview is for inspection. Read any retention warning before confirming; restore creates a new current version, while older history remains available subject to the product's policy. Reopen the current editor and verify the restored graph.

Related documentation

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

On this page

1 / 4
  1. The editor is offline
  2. Save failed
  3. A conflict appeared
  4. An older version is needed

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

Responsible useGlossary