Build a useful investigation brief
Align source and event chronology
Map source transaction begin and commit, event creation, identifier assignment, enqueue or acceptance, transport receipt, consumer claim, handler start, acknowledgment, projection update, and visible result. Compare timestamps and versions. Record missing evidence as unknown rather than inferring emission from the source write.
Inspect filtering and consumer outcomes
Compare event type, schema version, routing or subscription rules, consumer selection, validation, retry, dead-letter or review state, and projection write. Use a neighboring successful event with matching structure. Keep hypotheses separate from evidence when a filter or parser appears associated.
Test one safe delivery correction
Evaluate one change such as committing event creation with source state, correcting a filter, making acknowledgment follow projection success, or adding a bounded replay. Reproduce missing and successful paths, then check duplicate delivery, ordering, final state, and audit evidence before accepting recovery.
What to carry forward
Deliver an evidence-backed brief with event identity, source and delivery chronology, first missing boundary, consumer evidence, tested correction, replay risk, and uncertainty. Investigation is complete when implementation can target one delivery gap and verification can prove source, consumption, and outcome.
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