Save drafts and resolve conflicts
Persist valid changes, recover local work, and review concurrent edits before overwriting.
Save persists the app definition to Strive. Local draft recovery and Undo/Redo protect editing work, but neither means the current definition was saved to the server or activated as a fixed release.
Save a valid draft
The toolbar reports No problems or a problem count. Save is enabled when there are changes and the definition is valid. If it is disabled, inspect the reason: there may be no changes, schema problems, an in-flight save, or a conflicting lifecycle operation.
In Code view, Save commits pending text first. Invalid JSON or schema errors prevent saving the previous valid document in place of what you currently see.
Every successful save preserves definition history. Use Definition versions to compare or restore saved snapshots.
Recover a local draft
The builder periodically stores a local recovery draft. When its baseline still matches the server, returning to the editor can restore it. This recovery belongs to the browser's local storage; it is not collaboration or a durable substitute for saving.
A draft based on an older server version is set aside rather than silently imposed on the current app. Unaccepted agent-only work is likewise kept separate from your accepted working document. Read the notice and choose an explicit disposition. Do not clear browser storage if you still need a retained local draft.
Resolve a save conflict
Another tab, teammate with permission, or Assistant action can advance the definition while you edit. If Save conflicts, Strive loads the winning server version as the new baseline while preserving your local definition as the working document.
- Keep my changes: acknowledge the banner, inspect the current state carefully, and Save to apply your reviewed working document.
- Discard my changes: replace your local work with the latest server definition.
Keeping is not an automatic field-by-field merge. Review what your working document would overwrite, especially removed components, data-source changes, and event actions. Repeatedly retrying a stale version without review is not a conflict-resolution strategy.
Leave deliberately
Leaving with unsaved work prompts you. Save when you want a durable definition, or explicitly discard when you do not. Saving a design does not start a backend run, change the runtime pin, or activate an immutable release. See Releases.