Save, sync and recover work

Before you start

Prerequisites

A local diagram. An active signed-in account is needed for publishing.

Permissions and plan

Local saving needs no account. Account saving requires an active account and write access.

Steps

1. Choose Save to see the current save status and the available storage options. Local drafts autosave only in this browser.

2. Choose Diagrams → On this browser to open earlier named drafts or download their JSON backups. New diagrams and imports keep your earlier drafts.

3. Choose Download JSON backup to keep an editable copy outside this browser.

4. Choose Save to account. If signed out, use Sign in to save this draft; you return to Diagrams with your draft preserved.

5. Choose the intended owner and Save to account. Reopened writable account diagrams sync edits; wait for All changes synced.

6. Choose Save → Checkpoints → Create checkpoint to name a recovery point. Local checkpoints stay in this browser; account checkpoints belong to the saved diagram.

7. Use Review restore to inspect checkpoint differences before restoring. Recover draft in the diagram explorer can recover a previous local draft. Import model can open an exported backup as a new local draft.

8. To remove a browser draft, open a different draft first, then choose Move to Recently deleted. Restore it from Recently deleted; browser data is never automatically evicted by Flowboard.

Copy this model into Import in the editor. Export current work first. The two stable identifiers, api and db, connect the services to the flow.

# Request path

- API {#api type=service x=100 y=120}
- Database {#db type=database x=500 y=120}

## Flows
- api -> db {#requests label="requests" color=#f05a47 speed=1 direction=forward}

Change a label to describe your system. Keep the identifiers the same when you want existing connections to keep referring to those nodes.

Check your work

Expected outcomeA clear storage location, portable backup and recoverable checkpoint.

Next steps

Try the workflow in the editor, then use the reference for control details and model syntax.

If a step does not work, keep an export of your model and follow the troubleshooting guide. Include the error message when contacting support, without sharing credentials or private architecture.