What to do when 'All saved' is stuck on 'Saving…'

Wait 10 seconds, stop editing, check your network, then click the pill if it goes red. If it stays amber for more than a minute, here's the safe escape path.

~3 min read All users

Quick read of the pill

The save-status pill in the top-left of the Overture toolbar tells you whether your edits are being committed to the server. It has four states:

All saved (green, checkmark) — everything is committed. Safe to close the tab.
Saving N… (amber, spinner) — writes are in flight. N is how many are pending.
N failed · Retry (red, warning) — at least one save gave up after retries.
Offline · N queued (amber, no-wifi) — your browser thinks the network is down.

If the pill shows Saving… for more than 10–15 seconds, something is wrong. Walk through the steps below in order.

30-second triage

Wait 10 seconds first. Saves retry automatically with backoff. Most "stuck on Saving" cases clear in under 10 seconds.
Stop editing. Each new edit adds another write to the queue, which can make a backed-up queue look worse. Pause typing and let the queue drain.
Check your connection. Open any other site. If Twitter or Gmail also hang, your network is the problem. Switch networks (Wi-Fi to phone hotspot, etc.) and the pill should switch from Offline back to Saving and then to All saved on its own.
If the pill goes red ("N failed · Retry"), click it. Overture retries every failed write. If the error message mentions a session expiry, sign out and back in — the auth token rotated while you were editing.
Don't refresh while Saving is stuck. A refresh cancels in-flight writes for that tab. Refresh only after the pill is either green (all saved) or red (failed) — not while it's amber.

If it stays stuck for more than a minute

Copy any unsaved content you care about into a notepad. Just in case.
Check Overture's status — see Check Overture's live system status. A backend incident can stall writes for the whole platform.
Sign out and back in. This forces a fresh auth token and a fresh sync of the event. Your work is already in the queue — it'll replay on next sign-in if the network is reachable.
If you've already done a sign-out/in and it still won't drain, clear the local cache — see Clear local cache safely. Warning: this discards the in-browser queue, so any edit that hasn't yet committed to the server will be lost. Only do this if you've already manually saved the work elsewhere.

What's almost never the cause

Your edit being "too big." Overture chunks writes; size doesn't stall the queue.
Browser version. The save layer doesn't care which browser as long as the network is reachable.
Multiple tabs. Each tab has its own queue and they don't conflict at the save layer.

When to file a bug

If the pill stays stuck even after sign-out/in and you've confirmed Overture's status is green, send a report:

The event name.
How long the pill has been amber.
What you were editing right before it stalled (a row, a follow-up, a venue field, etc.).
Your Overture version — see Check Overture's version.
Browser and OS.

Send it to [email protected] or use the in-app Support button (life-ring icon). See How to report a bug to support.