Check whether the outcome improved
Define timing outcomes
Write expected receipt, response, retry, processing, and side-effect state for fast, slow, interrupted, failed, and repeated deliveries. State the point at which success is safe and which failures remain recoverable.
Run receipt and work paths
Execute fixtures through signature, durable receipt, acknowledgement, and asynchronous work. Confirm slow work cannot hold the response indefinitely and that a crash after receipt leaves a recoverable event. Check receipt persistence before measuring processing latency.
Check sender retry interaction
Repeat a delivery after timeout before receipt and after receipt. Verify deduplication and acknowledgement produce one intended effect. Inspect logs for timing and correlation without raw payloads or secrets. Keep the retry tied to the original event.
What to carry forward
Accept when valid events receive a timely response after durable receipt, slow work is recoverable, and retries do not repeat effects. Keep sender timing partial where uncontrolled. Record timing fixture, receipt store, handler revision, and side-effect result. Keep a response success from masking an absent receipt.
Technical background: Stripe documentation.
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