Keep the lesson for the next incident
Keep the identity evidence
Record event key, resource, state, version, source and delivery time, channel, retry, action, and history. Name the visible distinction between a retry and a legitimate repeat. This keeps a timing fix from erasing meaningful change.
Compare later streams
Review retry, cross-channel, inside-window, outside-window, and real-transition cases after the change. Look for continued noise or a hidden update. Preserve a stream where the window behaved correctly. Compare the stream with a deliberately separate event.
Refine one window check
Require future reviews to pair a retry with a real state change, test window boundary, and inspect latest action and history. Assign ownership and revisit date. Define the observation that would show suppression reduced noise without hiding work. Record which future stream would expose a boundary regression.
What to carry forward
The learning record connects one deduplication choice to later event evidence and a repeatable identity-and-window review. Stop when another reviewer can replay the identity window for another event class. Carry forward uncertainty where event identity or channel timing is incomplete.
Technical background: Android 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