> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jaantonio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recovery paths

> How people interact with automatic recovery, workspace retries, and corrective stamp work.

Most invoices never need this page. Use it when a document is stuck, when Lambda offers a retry action, or when you need to understand what support will do instead of guessing.

## Path map

```text theme={null}
Document stops
   │
   ├─ Transient / never started → automatic recovery (no corrective run)
   │
   ├─ Workspace offers Retry stamp / Retry delivery → take the labeled action
   │
   ├─ Source changed after review → accept/reject with evidence
   │
   ├─ Client fiscal fields need a validated overlay → fiscal correction preview → apply
   │
   └─ Misroute, version fix, or blocked failed row → support corrective retry
```

## Automatic recovery

Lambda's recovery watchdog looks for stamp work that can safely continue without changing fiscal intent.

<Steps>
  <Step title="Detect stuck work">
    Never-started invoices or durable attempts that can resume without remapping.
  </Step>

  <Step title="Continue exactly">
    Re-enqueue from persisted intent, or resume the current attempt with the same request and key.
  </Step>

  <Step title="Stop when unsafe">
    Exhausted recovery becomes a system error. Support starts a new corrective plan — recovery does
    not escalate into silent remap.
  </Step>
</Steps>

While automatic recovery is running, avoid duplicate manual stamps for the same document.

## Workspace: Retry stamp

When the invoice note's classification allows it, the workspace shows **Retry stamp**.

That action is still policy-bound: Lambda chooses resume vs reprocess from evidence. If the button is missing, the document is usually failed for review, waiting, already successful, or reserved for support — not “broken UI.”

Read the note and classification first: [Failures](/stamping/failures), [System errors](/stamping/system-errors), [Troubleshooting](/troubleshooting).

## Workspace: Retry CargoWise delivery

**Retry stamp delivery** or **Retry cancellation receipt delivery** only re-sends XML/PDF (or the cancellation receipt) to CargoWise inbound.

The CFDI may already be issued. Delivery retry does not call Facturapi to stamp again.

## Source change decisions

When later CargoWise evidence differs from what Lambda used, the workspace can surface a source-change decision.

* Accepting and retrying only proceeds when the change is retryable under policy.
* Rejecting leaves the fiscal document alone instead of forcing a remap.
* Post-stamp drift that would create a conflicting CFDI is not auto-healed by another stamp.

## Client fiscal correction

Some documents need a complete, Facturapi-validated fiscal profile before a corrective overlay is allowed on one planned attempt.

<Steps>
  <Step title="Validate the fiscal profile">
    Lambda checks the corrected client fields with Facturapi before any stamp plan is trusted.
  </Step>

  <Step title="Preview the plan">
    A plan hash is shown. Bulk corrections still preview first; nothing applies without that hash.
  </Step>

  <Step title="Apply with a reason">
    Confirming queues the corrective retry for the exact previewed plan. The reason stays on the ops
    run.
  </Step>
</Steps>

## Support-owned corrective retry

Support uses corrective retry when the workspace correctly blocks day-to-day action — for example a failed document after a proven mapper fix, or a misrouted invoice that needs a version-aware remap.

What you should expect from that path:

1. Evidence first (original capture vs current claim).
2. A fresh preview and plan hash.
3. Apply only that hash, with a ticket or explanation stored privately on the run.
4. Timeline claims such as resumed or reprocessed, then normal stamp terminal events.
5. No customer notification from retry itself.

Replacement of an already-issued Lambda-owned CFDI (cancel + related or unrelated replacement) is a separate, explicit support operation with a SAT motive. It is not the same as Resume or Reprocess above.

## What to do as the reader

| Situation                                  | Start here                                         |
| ------------------------------------------ | -------------------------------------------------- |
| Button says Retry stamp / Retry delivery   | Use it once; watch the timeline                    |
| Note says wait for parent or review fields | Fix evidence; do not invent a second stamp         |
| System error / support issue               | Leave for Jaantonio unless a safe retry is offered |
| You need the safety model                  | [Safety rules](/stamping/retry/safety)             |
| You need strategy meaning                  | [Strategies](/stamping/retry/strategies)           |