How Retry works

​

Mental model

Immutable CargoWise capture (original accounting evidence)
        │
        ├── Automatic recovery
        │     re-enqueue never-started work, or resume the exact attempt
        │     no remap · no new fiscal intent · no retry run
        │
        └── Corrective retry
              preview a plan → apply only that plan hash
              either resume the exact attempt, or remap source once
              durable run + reason · never silent

​

Evidence before mutation

1. Is this document already successful, cancelled, in flight, or waiting on a parent?
2. Does policy allow a stamp retry for the active classification?
3. Can we resume the exact stored attempt, or must we reprocess from the original capture?
4. For failed documents: is there proof the fiscal projection changed, or that an approved prerequisite was corrected?

​

Preview, then apply

1. Preview recomputes what would happen and returns a deterministic plan hash.
2. Apply recomputes under lock and only proceeds if that exact hash still matches.
3. A private reason is stored on the ops run. It is not copied into customer notifications.

​

Strategies in one line

• Resume attempt — continue the exact stored Facturapi request and idempotency key.
• Reprocess source — remap the original capture with current Lambda code and create one new attempt only when the prior create never produced a provider invoice.

​

Who owns what during recovery

​

Where this sits in stamping