Keep the lesson for the next incident
Write the state table
Document declined, unpaid timeout, pending, late success, paid-without-order, and duplicate-attempt states with one allowed next action each. State the record that proves each outcome and the condition that moves an unknown state forward.
Keep idempotency fixtures
Save controlled traces for a repeated submit, delayed response, refresh, and late success. Include attempt and order correlation without secrets. Assert that the same logical checkout cannot create a second financial outcome during recovery.
Define recurrence triggers
Reopen review when a timeout lacks a correlated status, a paid attempt has no order, or a retry creates another identifier unexpectedly. State sampling limits and ownership. Do not interpret a quiet period as proof that delayed outcomes cannot recur.
What to carry forward
Close learning with a state table, safe recovery wording, and correlation fixtures that protect one logical payment attempt. Keep unknown transitions and monitoring limits visible so a future timeout change receives the right scrutiny for later reviews.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow