Decide where the work belongs
Name the attention cost
Describe what repeated messages make hard to see and whether a person could miss a state change. Compare retries, repeated saves, and distinct transitions. Keep channel duplication separate from two events in the same channel.
Compare coalescing choices
Set update-in-place, grouped history, channel fallback, separate alerts, and no change beside one another. Consider whether each child is actionable and whether the latest state remains visible. Prefer a repair that reduces noise without erasing evidence.
Choose the first slice
Record event identity, channel, owner, and the next review date. Decide whether to fix identity, grouping, copy, or delivery mapping. Preserve the original stream and one legitimate repeat so the queue decision can be evaluated.
What to carry forward
Prioritize coalescing where repeated representations hide a meaningful action or state and identity is reliable enough to preserve history. The decision should name channels and exceptions. If repetition is legitimate and understandable, queue a different notification issue instead.
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