Recover a WebMCP Update After Its Response Disappears
Post · https://dev.to/gde/recover-a-webmcp-update-after-its-response-disappears-2hp
The browser showed JFK. The database already contained BOS. That was the state of a synthetic trip...
First seen by Oriel on .
AI summary
This Trip Workbench test shows WebMCP can safely recover a committed update after its response disappears by querying the original command, preserving local edits and avoiding a retry.
- A PATCH changing destination from JFK to BOS committed revision 3, but the client showed revision 2 and JFK after its HTTP 200 response was dropped.
- expectedRevision detects stale starting versions, while commandId identifies the logical mutation for authorized receipt lookup.
- recheck_trip_update queries only the unresolved editor command and confirms the original receipt without sending another PATCH.
- Recovery preserved the server’s saved purpose, the user’s newer local purpose edit, and hasUnsavedChanges: true.
- Independent assertions verified one PATCH, one matching receipt, database destination BOS, and visible unsaved work; later changes bounded lookups and handled 401 exits.
#webmcp #react #mutation recovery #idempotency
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Reactions
Total public reactions reported by the source; distinct from points and likes.
- DEV Community: 18, latest observation ; +2 over observed period since
Comments
Comment count reported by the source.
- DEV Community: 11, latest observation ; +4 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| DEV Community | 5031079 | https://dev.to/gde/recover-a-webmcp-update-after-its-response-disappears-2hp Read discussion |