Save and resolve conflicts

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.

Start lesson