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. /Save and resolve conflicts
IntermediateLast verified Sep 30, 2026

Save and resolve conflicts

Protect local edits, recover from offline or error states, and choose the correct version after a conflict.

On this page
  1. Prerequisites
  2. Save normally
  3. Recover from offline or error
  4. Resolve a conflict

Watch the save state before leaving the editor or starting an action that needs the latest version. A local edit is Dirty until storage accepts it. Saving is still in progress; only Saved confirms the most recent accepted graph. A checkpoint is a named history entry, not a replacement for resolving a failed current save.

Prerequisites

Sign in to an account with Flow Editor access and open a strategy you can edit. Keep this editor tab open until the save state is resolved.

Save normally

After a small, visible edit, such as changing Condition's literal threshold from 55 to 60, leave the field so the edit applies. Choose Save strategy, press Ctrl+S on Windows or Linux, or press Command+S on macOS. Wait for Saved. Autosave also runs while editing, but it does not remove the need to check its outcome. Exit and reopen the same strategy when you need proof that the value persisted; the reopened Inspector should show 60.

Recover from offline or error

Keep the editor open. Restore the network connection or use the retry action shown with the error. If the error points to a missing required value or permission, correct that cause instead of retrying unchanged input. Save again and wait for confirmation. Avoid refresh or opening another editable copy until the state is clear: neither action proves that local edits were accepted. If you must investigate a longer outage, record the strategy identity and the last confirmed version before leaving the page.

Resolve a conflict

A conflict means another accepted version changed while you were editing. For example, tab A changed the threshold to 60 while tab B saved 65 first. Tab A's next save must be resolved; neither value should silently win. The dialog offers Keep my changes and Reload server version. Choose the first only if tab A's full local graph is the state you intend to keep; choose the second if the accepted server graph at 65 should replace it. This is a choice of graph, not an automatic field-by-field merge. Do not repeatedly retry the same rejected write.

After resolution, check Condition's actual threshold and other changes, validate the current graph, save, and reopen it from Strategies to confirm the accepted version. If the reopened value is not what you expected, stop and inspect version history before editing again. The navigation guard warns about local changes for same-tab navigation; documentation links open separately so your editor remains in place.

Try it here

Practice a save conflict

Protect local edits, recover from offline or error states, and choose the correct version after a conflict.

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

Related documentation

  • Saves, versions, and checkpointsUnderstand dirty state, autosave, conflicts, history, and non-destructive restore.
  • Create checkpoints and restore versionsCreate a named recovery point, preview history safely, and restore without deleting older versions.
  • Troubleshoot save, offline, and conflictsProtect local edits and recover when the editor cannot confirm the latest saved version.

On this page

1 / 4
  1. Prerequisites
  2. Save normally
  3. Recover from offline or error
  4. Resolve a conflict

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

Responsible useGlossary