Decide where the work belongs
Name the visibility cost
Describe what the person needs to know and whether the event remains reviewable. Compare a muted optional update with an important workflow state. Keep channel failure separate from a user choice not to be interrupted.
Compare alternate paths
Set in-app record, email, browser, mobile, manual refresh, and no fallback beside one another. Consider deduplication, timing, and copy. Prefer an alternate path that preserves action context without violating the selected preference.
Choose a bounded move
Record event class, preferred channel, owner, and fallback evidence. Decide whether to improve durable status, fallback mapping, or duplicate guard. Preserve preferred-success and preferred-disabled controls for evaluation. Keep the alternate path visible without implying delivery. Name the durable record that should carry the event.
What to carry forward
Prioritize fallback where an event can become invisible despite a durable need or where alternate channels create duplicate noise. The decision should name preference boundary and remedy. If the in-app record is clear and no duplication occurs, queue a different delivery issue.
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