Forms
Save Form edits and recover from conflicts
Distinguish autosave from dialog drafts, retry failed saves, and use session Undo without losing local work.
The Form builder saves changes to the current Library Form. There is no separate publishing step. You need continued folder edit access, workspace authoring access, and available storage.
Confirm that your edits saved
- Make the change and finish any item or settings dialog with Done.
- Finish pending image operations.
- Wait for Saving… to disappear from the builder header.
- Check for a Save failed notice before continuing.
- Use Preview to inspect the saved Form, or the builder's Back control to return to Library.
Ordinary builder edits save after a short pause. Adding, deleting, moving, and applying settings also trigger saves. Preview and the normal builder Back action wait for pending builder changes to save; failed saves keep you in the builder.
The Form header does not retain a visible Saved badge after success. Disappearing Saving text does not mean an unfinished dialog has been applied. Item dialogs use Done; Form and Section settings use Done as well.
A browser warning about leaving unsaved work does not save it. During recovery review, automatic saving is paused and you must explicitly save or return to the saved version.
Retry a failed save
Keep the editor open. Read the message, check your connection, access, storage, and entered settings, then choose Retry save.
If an item dialog reports failure, resolve the underlying problem and try Done again. Wait for uploads or other image operations to finish before trying to save or leave.
A failure can occur after some Form changes have already been accepted. Do not assume every part of a failed attempt was rolled back.
Resolve a competing edit
If the Form changed elsewhere, preserve needed work through Saved drafts and Download draft. Finish or discard an open item dialog before changing the builder version.
Choose Use saved version to load the current server Form. This replaces the editing view and resets its Undo history; it does not merge edits. Review the latest content before reapplying your changes or reviewing a retained draft.
If editing is paused because storage is full, use Back to Library to remove unneeded content. Preserve unsaved work first; leaving through the storage notice is not a substitute for a successful save.
Use Undo and Redo
The header's Undo and Redo act on recent builder changes. Outside dialogs, Ctrl/Cmd+Z undoes; Ctrl/Cmd+Shift+Z or Ctrl/Cmd+Y redoes.
History retains up to 50 changes in the current editor session. Nearby typing may be grouped. A new edit clears Redo. Reloading, reopening, or restoring a recovery draft resets history. A successful refresh after Form Agent changes also clears Undo history. For competing local edits or a failed Agent refresh, use editor recovery.
Undo saves the restored content and can fail like another edit. It does not restore cover-image changes, uploaded file bytes, or another editor's history. Use settings to change a cover explicitly.