Skip to main content
Most documents stamp once and finish. Recovery covers the cases where work stalls or must continue with proof. Two lanes stay separate on purpose: 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 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.

​
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

Day-to-day invoice work starts with Workspace. Read this section when you need to understand what Lambda will resume, remake, or refuse.