> ## 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

> What Lambda fixes automatically, and when a deliberate corrective retry is required.

Most documents stamp once and finish. Recovery covers the cases where work stalls or must continue with proof.

Two lanes stay separate on purpose:

| Lane                   | Job                                                                           |
| ---------------------- | ----------------------------------------------------------------------------- |
| **Automatic recovery** | Keep stuck work moving without changing what Lambda already intended to stamp |
| **Corrective retry**   | Change course only when durable evidence says a correction is required        |

Recovery is not “press again until it stamps.” It is not a second stamp for a document that already has a SAT UUID. It is not CargoWise delivery retry — delivery of XML/PDF is a separate lane.

## Automatic recovery

Lambda looks for stamp work that can safely continue without remapping:

* Documents that were accepted but never started
* Mid-flight attempts that can resume exactly as prepared
* Limited retries when a system stamp error is proven safe to retry

While automatic recovery is running, avoid duplicate manual stamps for the same document. When recovery budgets are exhausted, the document becomes a [system error](/stamping/system-errors) and needs a fresh corrective plan.

## Corrective retry

Corrective retry is deliberate. It only runs when policy and proof allow it — for example after a mapping fix, a validated fiscal correction, or accepted source-change evidence.

You may see **Retry stamp** in the workspace when Lambda already allows a safe continuation for that classification. If the action is missing, the document is usually waiting, already successful, failed for review, or reserved for support — not “broken UI.”

Details: [Corrective retry](/stamping/retry/corrective).

## What never happens

* Re-stamping a successful or cancelled CFDI through everyday recovery
* Quietly remapping to match post-stamp CargoWise drift
* Treating delivery problems as a reason to stamp again

## Who meets recovery

| Audience              | How they meet it                                                                                   |
| --------------------- | -------------------------------------------------------------------------------------------------- |
| **Accountants / ops** | Workspace actions like **Retry stamp** when offered, or fiscal-correction flows that preview first |
| **Admins**            | Delivery retries never re-stamp; some corrections stay support-owned                               |
| **Support**           | Corrective paths for misroutes, version-fixed remaps, and cases the workspace correctly blocks     |

Day-to-day invoice work starts with [Workspace](/stamping/workspace/overview). Read this section when you need to understand what Lambda will resume, remake, or refuse.