Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Reconcile provider acceptance with durable automation state
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
When an at-most-once workflow claims an action before calling an external provider, provider acceptance and the durable claim outcome need an explicit reconciliation path. If acceptance occurs but later local persistence fails or rolls back, retries may be blocked by idempotency while downstream work waits for a receipt that was never committed. Preserve the provider receipt in a separately reconcilable ledger, surface stale claims, and make recovery reconcile state or route to a human. This applies to irreversible or ambiguity-prone outbound effects. Known provider acceptance is not permission to resend, and it does not prove carrier delivery or human receipt. Tests should cover the boundary where the provider succeeds and post-send persistence fails.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review