D07
Recover without duplicating work
Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.
Read the typed error’s code, retry_action and usage_state. HTTP status alone is insufficient, especially after an uncertain completion. Keep the safe request/operation reference for support; do not include secrets or complete private payloads by default.
| Recovery instruction | Your action |
|---|---|
correct_request |
Review the permitted field/reason guidance. A changed semantic request requires its own explicit operation. |
reauthenticate |
Restore the required current authority. Authentication success alone does not authorise replaying a mutation. |
wait_then_retry_same_operation |
Respect the applicable wait guidance, retaining the original request and logical-operation identity. |
poll_operation |
Inspect the original operation through its permitted status path; do not replace it with a new request. |
start_new_operation_explicitly |
Decide whether to start a new operation under normal scope and cost admission; it is not an automatic retry. |
do_not_retry |
Stop automatic retries and follow the explanation or support route. |
For operation_in_progress or completion_uncertain, keep the original operation. A timeout or closed browser tab is not proof that work was cancelled. If a result is restricted, invalidated or expired, follow the current rights and recovery guidance; repeated retries cannot restore withdrawn rights.
Business recovery suggestions are different from transport retries. They can ask you to clarify the country, supply a registration identifier or address context, reconcile conflicting identifiers, or review candidates. They can also tell you to stop for unsupported scope or missing evidence. These suggestions do not guarantee a match or authorise repeated paid searches. Unknown future recovery codes should stop automation and lead to compatible documentation or support.
If a dependency fails, treat it as a technical failure. Do not turn it into a successful empty result, remove contradictory input to force a match, or manufacture a field to satisfy an example.
A later authentication refusal describes that attempt only. It does not prove an earlier uncertain operation had no effect. Retain the original intent, key and creation time, restore current authority, then reconcile through the compatible original-operation route.