Before closing the editor, look for an explicit saved status. If a change is missing when you return, first check that you opened the same workflow and version. Saving a draft does not make it a released version available for execution.
The editor normally saves edits automatically after a short pause, approximately half a second. A network request and any queued work still have to finish. Wait for Saved rather than relying on the elapsed time alone.
Read the save status
The header indicates when saving is in progress, when a save has completed, or when a save failed. A new workflow can initially show Not saved.
If your editor displays a manual Save control, use it and check the resulting status. Autosave is the normal mode; do not assume a manual Save button is always present.
There is no Cmd/Ctrl+S editor shortcut for forcing a save.
The header currently shows Not saved. Undo, History, and Redo are in the same toolbar. After an edit, wait for Saved before leaving the editor.
Undo, redo, and History
Use the header controls to undo or redo workflow edits. The keyboard equivalents are:
Undo: Ctrl+Z on Windows/Linux or Cmd+Z on Mac.
Redo: Ctrl+Y on Windows/Linux or Cmd+Shift+Z on Mac.
Move focus out of a text input first when you intend to undo a workflow change. Text inputs, rich-text editors, and the import spreadsheet can handle their own undo.
Open History to inspect saved changes and return to a previous state. History concerns editing states; More → Versions concerns workflow versions and releases.
More → Versions opens Version Management. Version 0 is marked Current and Latest, while Published has no date. Latest does not mean published. Use the editor header for the save status and History for editing states.
When saving fails
The save-error dialog automatically retries at intervals. It shows progress and provides copy controls for diagnostic information.
Keep the page open while the retry is in progress.
Check your connection and whether the platform is reachable.
If retries do not resolve the issue, copy the displayed diagnostics for your administrator or support.
Before using Refresh Page, preserve any important unsaved text you can still access.
Do not assume an unsaved edit exists in server history. Saved changes and work that never reached the server are different.
Editing locks
A session-taken-over or session-expired message requires a different response from a transient save failure. Coordinate with the other editor where relevant, then follow the reload instructions.
Before you leave
Confirm Saved. If you need to release the changes to operators, separately validate, test, and publish the workflow. Closing a saved draft does not publish it.
Hand over editing
If another editor holds the temporary lock, coordinate before using Take Over Editing. Ask them to finish and confirm Saved. Takeover can interrupt unsaved changes. The previous editor can see Session taken over and a Reload action when the conflict is detected. Session expired means the lock is no longer valid; coordinate ownership and follow the reload instruction.
The editor attempts to release its lock on exit. For a stale lock, use the coordinated handoff process. This lock differs from locking a workflow version. History cannot guarantee recovery of work that never reached the server.