Recover uncertain review requests
Resolve lost responses without duplicating edits, decisions, or paid generation.
An uncertain request is one for which the browser did not receive a definite outcome. The action may already have committed. Treat this differently from a confirmed refusal or validation error.
Use the existing retry
When the review offers an explicit retry for an uncertain action, it preserves the original request and intent. Retrying that exact action can recover the original event rather than applying it twice.
Do not change the payload or source options and try to reuse the old uncertain intent. A different body is a different action. A stale review revision also requires reload and a new decision rather than forcing the earlier change through.
After reload
The generic review component retains an uncertain request in memory. Reloading discards that pending browser request, while the persisted review and events remain. Reopen the saved review and inspect its current status, revision, and history before submitting another action.
For generation, read the saved attempt receipt. An interrupted attempt can remain unknown, and its budget reservation may still be held. Starting another generation can incur another charge without explaining what happened to the first one.
Recovery checklist
- Identify the review and action you attempted.
- Read its current revision and latest events.
- Inspect the original receipt or generation attempt where available.
- Retry only through the action's retained recovery path when it is still available.
- Make a new deliberate change only after the existing outcome is understood.
A recovered old event can coexist with later edits. Check the current projection as well as the recovered receipt. Success for an earlier revision does not mean the review is still approved after a later payload change.
See history, generation, and decisions.