Auto-saving edits are invisible unless the UI says something. A per-member pill appears immediately on change, turns green for a moment on success, and turns red for four seconds on failure — and a failure re-reads the roster so the rejected value does not stay on screen.
Also called: did my change save · saving indicator · edit didn't stick
- 1updateMember sets a per-id state of saving | saved | error.
- 2On failure the error is logged, the pill shows Save failed, and a refresh key bump re-pulls the roster.
The comment records what it replaced: 'Previously the only signal was the role button visually highlighting, which didn't differentiate saved locally from saved to Clerk.' The rollback has its own note — leaving the rejected value on screen 'is how an admin walks away believing an edit stuck'.
- Auto-save gave no confirmation that anything reached the server.
- A failed write left the optimistic value visible, so the admin believed it had saved.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →