How Your Changes Save
Summary
Spring Hub saves most changes in the background. The screen updates straight away while the write continues on its own — you do not wait for a spinner and you can keep working or move to another screen. The header next to your account menu shows how those saves are going.
How to
Read the header save status
| Header shows | Meaning |
|---|---|
| Nothing | Everything is saved. |
| Saving… / Saving 3… | Changes are still being written. Keep working. |
| Green All changes saved | The last change landed (shows briefly, then clears). |
| Red 1 not saved | A change could not be saved and was undone on screen. Click it to fix. |
Some apps show extra save cues on the row or card (for example Saving… over a fabric photo, or a faded comment until it lands). The header is always the place to check overall status.
When a save fails
- Click the red 1 not saved button in the header.
- Changes not saved lists each one with the reason it was rejected.
- Use Retry to try that change again, or Dismiss to keep it undone.
- With more than one failure you also get Retry all and Dismiss all.
A change that fails is reverted on screen, so what you see always matches what is stored. Brief network drops are retried automatically; you only see the red button when the change was actually rejected (for example a permission or validation problem).
If you reload the page or close the tab while Saving… is showing, your browser warns you first. Wait for the header to clear before closing.
Actions that still make you wait
Some actions block on purpose because you need their result:
- Excel and PDF exports
- AI photo reading and analysis
- Sign-in
Deleting still asks for confirmation first.
Explicit Save buttons
Most edits do not need a Save step. A few flows still use an explicit Save when you are creating the first record (for example the first Save on a new Designer Selections sheet). After that, further edits on the same record follow background saving like everything else.
Wizard autosave (Inspection Reports)
Inspection Reports uses its own report header, not the account-menu save status:
| Control | What it does |
|---|---|
| Draft saved | Autosave status (with time). Progress is kept as you move through the form. |
| Clear Draft | Discards the whole inspection (cannot be undone). |
| Next | Saves the current step and moves forward. |
Do not use Clear Draft unless you intend to discard the whole inspection.
Exceptions and Escalation
- Red “not saved” keeps coming back after Retry — the change is being rejected, not lost. Read the reason in the popover, fix the input, and escalate to IT / platform admin if the reason is not clear.
- Browser warning on close — a save is still in flight. Wait for the header to clear.