ORDER-A · receipt committed
The receipt exists.
The response doesn’t.
A’s receipt is committed. The configured fault interrupts the response. Retrying now could fulfill the order twice.
The failure lab for queued workers
A retry can fulfill twice. A careless fix can lose a valid order. ReplayGuard catches both.
Recorded local comparison · simulated fulfillment.
Separate AWS observations are linked below.
Scroll to follow the failure 01 — 04
ORDER-A · receipt committed
A’s receipt is committed. The configured fault interrupts the response. Retrying now could fulfill the order twice.
ORDER-B · same product, different order
B requests the same product. The product key raises a payload conflict and leaves B without a receipt.
ORDER-A · delivered again
Without a key, A’s retry creates another receipt. Both keyed handlers reuse A’s original receipt.
ORDER-B · returns in a new message
B returns through another message. Only the order key finishes with one receipt for A and one for B.
One crash. Three choices of key.
Each order has one receipt. The other repairs duplicate work or lose ORDER-B.
Final counts checked against independent receipt snapshots.
Inspect the repair
Choose a handler. See every case it passed, broke or could not resolve.
Bundled local comparison. The opening story always follows this recording; imported files only change this inspector.
Captured Python source files. Hashes identify the supplied code; they do not authenticate the report’s origin.
Your file stays in this browser. Importing checks the supplied observations; it does not run Python or authenticate their origin.
A small test. A useful habit.
Change the key from order to product. Watch a valid order lose its receipt. Restore the key, and keep the same case as a regression.
Download the regression kitExtract the kit, then open a terminal in its folder.
Python 3.11+ · macOS or Linux · No packages or AWS credentials
def build(effects):
def handle(delivery):
order = delivery["order"]
return effects.fulfill(
order, key=order["orderId"]
)
return handleImport before.json after the command finishes.
Your trusted Python adapter connects to the simulated receiver. Read the adapter guide.
Check the limits: the full example suite includes three handlers and deliberate evidence-limit controls. An aggregate Unresolved / exit 3 is expected.
python3 -I -S scripts/test_repair.py --output repair-results.jsonThe two-order AWS experiment
Three keys. Two valid orders.Recorded AWS evidence · experiment passed
Earlier AWS experiment · 18 September 2026
A Lambda worker crashed after simulated fulfillment succeeded. Standard SQS redelivered the message. A separate observer counted the receipts in DynamoDB.
Inspect the recorded AWS evidence16 assertions passed in the recorded AWS run.
The experiment stacks were removed after capture. AWS Amplify hosts the current viewer. New regressions run locally; this replay makes no AWS calls.