The editor does not have a standard Save button. Changes to an existing named template are sent automatically, and the top bar displays whether they are pending, saving, or already confirmed.
What you will learn
- Understand the autosave delay.
- Read the save status in the top bar.
- Know when the editor does not retry a request.
- Safely leave after completing your work.
How autosave works
The editor tracks field changes, drag-and-drop actions, insertions, pasting, and custom structural events. After the last change, it waits for several hundred milliseconds.
Before saving, the client compares the current configuration with the last confirmed state. A standard autosave updates the current state without creating a new history point. Major operations can independently create a commented checkpoint.
Safe working habits
- Perform one logical change, such as editing a module title or adding a row.
- Watch the indicator in the top bar. It may first display a pending or saving status.
- Wait for a confirmed clean state. Only then close the tab or navigate to another page.
- In case of an error, avoid rapidly making many further adjustments.
- If the status remains in an error state, check your connection and login session.
Saving requires an existing named template. In read-only preview mode, autosave is disabled. Additionally, the server will reject an invalid configuration.
How to read status changes
After an edit, the indicator may briefly notify you of unsaved changes, followed by a saving indicator, and finally a clean state. When performing multiple inputs in quick succession, you don't need to wait after every single keystroke; everything is merged into one current snapshot. Wait until your logical edit is complete.
Autosave does not guarantee the last millisecond
If you close the tab immediately after pressing a key, neither the delay nor the network request may finish running. Always wait for a confirmed save status before leaving.