Keep the lesson for the next incident
Document identity and revision
Write down the logical identity fields, mutable fields, revision semantics, and legitimate repetition cases. Include exact repeats, conflicting copies, and similar distinct examples. State what happens when the key is absent or reused so the contract guides review instead of encouraging silent grouping.
Keep delivery fixtures
Add compact cases for retries, reordering, delayed delivery, changed revisions, and legitimate repeated events. Assert logical count and downstream totals where they mattered. Preserve source-shaped metadata and expected outcomes so the fixtures explain the failure boundary rather than only the final deduplication result.
Review recurrence
Assign owners for source keys, ingestion behavior, and affected reporting when responsibilities differ. Review repeat rates and conflicting copies by source or release on a defined cadence. Set a reopening trigger for new identity variants, unexpected count inflation, or a changed repeat pattern.
What to carry forward
Close the learning record with identity and revision rules, delivery fixtures, owners, and a recurrence trigger tied to repeat behavior or count changes. Keep ambiguous historical groups visible. The lasting outcome is faster classification and safer decisions about repeats, not a promise that every source is perfectly idempotent.
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