Ownership Diagram Auto-Save
Ownership diagrams use a working-copy auto-save model. You can edit normally, and StructureGram persists the latest diagram state in the background.
What Auto-Save Covers
For ownership diagrams, auto-save persists your current working copy, including:
- Entity positions after manual movement
- Link routing/vertices after manual adjustments
- Routing settings, and which relationship lines you have edited by hand — so a diagram you rearranged last week still reads Manual-layout when you reopen it
- Related layout state needed to restore the same diagram view
The latest working copy is reloaded when you reopen that diagram.
Save Status in the Toolbar
The save indicator in the toolbar shows the current sync state:
- Saved: Working copy is synced to the server
- Changes pending: Edits are queued for the next auto-save cycle
- Saving: Auto-save is currently writing
- Save failed: Latest write failed; local state is ahead of persisted state
When save fails, use Retry in the toolbar.
Auto-Save Timing
Auto-save is debounced. StructureGram waits briefly after you stop interacting, then saves in the background.
This keeps editing responsive while still persisting changes quickly.
Auto-Save Workflow
Auto-save handles normal ownership diagram persistence. You normally do not need to press a save button after moving entities, changing link routes, or adjusting diagram presentation.
Typical uses:
- Watch for Saved before leaving a diagram after major edits
- Use Retry if the toolbar shows Save failed
- After a transient network issue, wait for the next successful save before exporting or reloading
Returning to Generated Layout or Clean Routes
The Refresh row at the top of the layout panel rebuilds part of the diagram. Each button is green when it has nothing to discard and amber when it does — see Understanding Auto-layout and Manual-layout.
Use Refresh ▸ Layout when you want StructureGram to recalculate the whole ownership diagram geometry.
Use Refresh ▸ Links when entity positions are useful but relationship lines need tidying — it rebuilds the lines, including any you edited by hand, without moving entities. With Direct or Tracks, moving or resizing an entity re-routes its links automatically, so you often won't need this at all.
Scope and Limits
- This model applies to Ownership diagrams
- Family Tree diagrams currently use explicit layout save behavior
- Auto-save persists the working copy; it does not create immutable milestone snapshots
- Scenario steps have their own saved working state after they are created
Troubleshooting
Status stays on "Save failed"
- Click Retry
- Check network connectivity
- If needed, make a small edit and wait for the next cycle
I do not see my latest layout after reload
- Check whether the status reached Saved before reload
- If it showed Save failed, retry first, then reload
Links did not refresh
- If a route refresh fails, the existing saved layout is not intentionally changed
- Refresh the browser page if the routing engine failed to load
- Try Refresh ▸ Links again after the page reloads