Resolve an unknown outcome

Before you begin

• The original operation reference, its account/device scope and the affected document/artifact identity.
• Access to the original journal and eligible read-only inspection path; preserve current evidence.

Follow the steps

1. Pause dependent changes

   Stop further writes, connector update/removal and replacement attempts that depend on the uncertain document result. Keep the document and journals.

   Checkpoint: No new affected write obscures whether the original edit happened.

2. Find the original reference

   Open the structured activity/recovery entry for the uncertain operation. Keep its exact ID and selected document, rather than using a fresh request to test the outcome.

   Checkpoint: The status/reconciliation request refers to that same original operation.

3. Inspect without applying

   Use the available Reconcile/read-status action. It reads journal, affected identities/revisions and artifact receipts; it must not open a new mutation transaction or repeat the command.

   Checkpoint: The result carries evidence for not dispatched, succeeded, failed with no effect, partial effect or still unknown.

4. Follow the classified result

   For succeeded, inspect/import the existing verified receipt. For proven not-dispatched/no-effect, review a new intent only after fresh context. For partial effect, inspect the actual remaining state before planning recovery.

   Checkpoint: The next action is based on the original effect classification, not on a timeout or a generic success banner.

5. Keep unresolved outcomes held

   If manual edits or missing evidence prevent proof, leave reconciliation required. Preserve safe references and ask Support. Only a matching outcome for this operation can resolve its hold.

   Checkpoint: A delayed receipt from another operation cannot clear the current unknown.

6. Check usage separately

   Read the original provider reservation/receipt under its frozen wallet. Native cancellation, no-effect or reconciliation completion does not independently settle model usage.

   Checkpoint: Native outcome and financial outcome each have their own known or pending record.

Check the result

• The exact original operation has a supported outcome with evidence, or stays explicitly unknown.
• No duplicate edit, automatic undo, blind refund or unrelated receipt is used to manufacture completion.

If something goes wrong

• The original reference is missing or the status action is unavailable.

  Keep the hold. Record build, host/document label, time and redacted activity references for Support. Do not invent a replacement status request or send the edit again.

  Resume from: Original operation recovered by an authorized inspection path.

• The host was manually edited after the uncertain operation.

  Preserve that fact and current document. Read-only comparison may be insufficient; keep unknown instead of guessing from visible geometry.

  Resume from: Enough original evidence for a supported classification.

• You canceled or the watchdog expired.

  Read the original state. Cancellation after dispatch is cooperative; watchdog expiry neither kills the host nor proves rollback.

  Resume from: Proven original effect, not elapsed time.

Continue with a related guide

• Recover the original workspace
• Export safe references
• Understand pending usage
• Get help with a held operation