Aglet

Verify notification channel fallback without duplicate alerts

Verification should prove that a durable event remains understandable when a preferred channel is unavailable and that fallback does not produce confusing copies. Test success, mute, denial, and failure paths, then inspect identity, timing, copy, and recovery. State what a person can still learn from the durable record.

Check whether the outcome improved

  1. Check preferred success

    Use a normal event and confirm preferred channel, in-app record, action, and absence of unnecessary fallback. Record identity and timing so a later failure can be compared. Compare that record with a muted preference.

  2. Check muted or failed channel

    Disable or fail the preferred path and verify the documented alternate or durable record appears with clear state. Confirm the person can act without receiving a duplicate version of the same event.

  3. Review recovery and copy

    Re-enable the channel, revisit history, inspect status, narrow layout, and settings link. State tested channels and platform limits. Leave a partial pass when external delivery or permission state cannot be directly observed. Check the fallback copy against the preferred channel wording.

What to carry forward

Verification passes when the event remains visible within the preference contract, fallback is proportionate, and duplicate identity is preserved. If a channel or platform is untested, document it. An extra message is not a passing fallback if the original event was already clear.

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