Keep the lesson for the next incident
Keep the event boundary
Record event key, resource, state, version, retry, channel, notification ID, action, and history. State whether the user sees a repeated message or a separate update. This prevents a later volume fix from erasing a meaningful transition.
Compare later streams
Review retries, multi-channel copies, repeated saves, and a distinct transition after the change. Look for an event that remains noisy or a legitimate update that disappears. Preserve a stream where coalescing behaved correctly.
Refine one dedup check
Require future reviews to pair a retry with a real state change, inspect retained history, and test the latest action. Assign ownership and revisit date. Define the observation that would show the check reduced noise without hiding work.
What to carry forward
The learning record connects one coalescing decision to later event evidence and a repeatable identity-and-state review. Stop when another reviewer can test a retry and legitimate repeat. Carry forward uncertainty where channel delivery or event identity 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