Check whether the outcome improved
Write stage acceptance
Define the expected identity, endpoint, arrival, acknowledgement, processing, response, state, and review record for completed, rejected, retried, duplicate, and interrupted deliveries. State which missing stage is an explicit unknown rather than a pass.
Exercise trace boundaries
Run each fixture and compare stage presence, identifier continuity, timestamps, response class, and downstream effect. Confirm a retry remains linked to the original event and an interrupted attempt cannot look like successful completion.
Check retention and recovery
Repeat a delivery after the configured evidence window or receiver restart where safe. Verify the remaining trace still distinguishes receipt, processing, and outcome. Record any sender or remote history that the local fixture cannot validate.
What to carry forward
Accept when success, failure, retry, duplicate, and interruption cases preserve safe identity and an honest stage outcome. Keep verification open for untestable remote history or expired evidence. Record fixtures, environment, retention boundary, and residual uncertainty with the result.
Technical background: Zendesk developer 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