Build a useful investigation brief
Build paired delivery fixtures
Create fixtures for a completed event, delayed processing, rejected validation, duplicate delivery, receiver interruption, and a delivery with an intentionally missing trace field. Record expected stage records and state before running them.
Follow identity across stages
Capture safe event and delivery identifiers, endpoint, timestamps, response class, worker attempt, final state, and review record. Compare the first divergence between working and failing cases. Keep arrival time from substituting for an identity match.
Change one observability input
Vary one correlation field, asynchronous handoff, retention window, receiver revision, or endpoint condition. Compare which stage becomes visible and whether state changes. If the sender report cannot be checked, name that boundary as an evidence limit.
What to carry forward
The brief is ready when paired deliveries reproduce the missing stage and show the first divergence, affected state, and remaining unknowns. Recommend the smallest safe evidence or repair change. Leave sender-only claims unresolved when receiver records cannot distinguish reach from retention.
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