A client can lose a response after a server has committed a change. Showing “nothing was saved” in that case claims knowledge the client does not have. Automatically repeating the request may create a duplicate.
Preserve the user's input
Keep the draft while explaining that the outcome is uncertain. Reload the authoritative record before deciding whether another write is needed.
Design a retry contract
If an operation needs safe automatic retries, define its identity and deduplication behaviour on the server. A spinner or retry button cannot establish that guarantee by itself.