Autosave and recovery

How account projects save

An opened account workflow loads its server snapshot. Edits are staged as a browser draft and a debounced server save follows after about 1.2 seconds; hiding the page also attempts to flush the latest change.

1. 1.Finish a small edit and allow the save request time to complete.
2. 2.Watch for a bottom error notification before closing the page.

Stay below the snapshot limit

Both remote workflow snapshots and local drafts have a 3 MB JSON limit. Inline unarchived media cannot be safely persisted as ordinary browser draft content.

1. 1.Archive media through the supported upload path rather than pasting a huge base64 string into a node.
2. 2.Split an oversized graph or remove large node content when a size warning appears.

Recover a newer browser draft

On reopening a server workflow, the editor compares the browser draft timestamp with the server update time and loads the newer draft. If the server is temporarily unavailable, an existing draft can be restored instead.

1. 1.Reopen the same project in the same browser if a network save failed.
2. 2.Inspect restored nodes and wait for reconnection before trusting cross-device availability.

Local canvas is different

The local canvas loads and saves to browser storage without a server workflow ID, with a roughly 300 ms save debounce. Clearing site data or changing browsers can remove this draft.

• •Treat a local canvas as a device-bound draft, not a shared account project.
• •If local storage is full, stop editing and preserve source media separately.

Read the save error

The editor distinguishes expired login, missing access, another tab changing the revision, oversized payload and offline/server errors. A browser draft is a fallback, not proof that the remote save succeeded.

1. 1.On a revision conflict, review the latest remote version before overwriting work.
2. 2.For offline errors, reconnect and make a further edit to retry; verify the warning disappears.

Example: embedded media warning

A pasted data URL may display in a node while still being unsuitable for persistent storage. The editor can save the graph structure but warns that unarchived embedded media must be uploaded again.

1. 1.Keep a copy of the original media file.
2. 2.Upload or archive it through the canvas/media path and verify the reopened node uses a stable URL.

Avoid competing browser tabs

Remote saves include an expected revision. Two tabs editing the same project can produce a conflict; the newer browser draft is not automatically a merged version of both tabs.

• •Use one active editing tab per project when possible.
• •If a conflict appears, inspect both versions before closing either tab.