Keep the lesson for the next incident
Record state semantics
Document which record proves payment, order creation, and confirmation readiness. Define what the shopper sees while each state is pending and which actions remain safe. Include the unknown state explicitly instead of hiding it behind a generic error.
Keep recovery traces
Save redacted traces for slow persistence, refresh, back navigation, late success, and repeated submission. Assert the same order identity remains visible. Link traces to the work record so a screenshot cannot be mistaken for complete timing evidence.
Define recurrence signals
Reopen review when confirmation is absent after a known terminal record, a retry is enabled before status is known, or order and payment timestamps diverge unexpectedly. State sampling limits, owner, and remaining asynchronous unknowns.
What to carry forward
Close learning with a state table, safe recovery traces, and recurrence conditions tied to the records that matter. Keep timing limitations visible so future confirmation work can distinguish a slow success from an unsafe unknown state.
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