Keep the lesson for the next incident
Keep the timing promise
Record event, time zone, schedule, urgency, channel, in-app state, delivery status, and copy. State whether the event was delayed or unavailable. This prevents a later review from treating all quiet periods as one behavior.
Compare later schedules
Review another user time zone, boundary minute, urgency class, and history state after the change. Look for a schedule that hides the event or copy that implies it was lost. Preserve a normal-hours control.
Refine one timing check
Require future reviews to compare quiet and normal windows, state time zone, inspect in-app availability, and test a recovery action. Assign ownership and revisit date. Define the observation that would show the check reduced false “missing notification” reports.
What to carry forward
The learning record connects one delayed-alert misunderstanding to later timing evidence and a reusable quiet-hours check. Stop when another reviewer can replay the timing contract for another event class. Carry forward uncertainty where device scheduling or platform delivery remains outside the app’s control.
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