Check These Settings Before Blaming Your Alarm App

Yes, your phone can quietly swallow an alarm app’s notification even while the alarm sound itself goes off fine, and the setting responsible usually isn’t the one people check first. Two different iOS and Android features do this: notification-summary batching, and Do Not Disturb’s per-schedule app lists. Neither kills the app in the background the way Android’s battery optimization does, and neither is the Critical Alerts entitlement gap that governs whether the base alarm can override a muted phone at all. This is a third, narrower problem: the app is running, the alarm rings, and a follow-up notification (a missed check-in nudge, an escalation to a friend, a “you still haven’t confirmed” alert) still doesn’t show up when it should.

iOS: two settings to check

1. Open Settings > Notifications > Scheduled Summary. If it’s on, check whether your alarm or accountability app is in the included-apps list. Summary doesn’t block notifications outright; it holds them and delivers a batch at whatever times you’ve set, up to 12 a day. A follow-up nudge that lands in a 6 p.m. summary instead of the moment it was sent might as well not have arrived.
2. Remove that app from the summary list, or set it to “Immediate Delivery” per-app from the same Scheduled Summary screen. This is separate from Focus mode entirely; a phone with no active Focus can still defer notifications this way if summaries are on.
3. If your active Focus is the suspect instead of Summary, the fix lives at Settings > Focus > [the active Focus] > Apps, and a full walkthrough of that specific setting already exists here rather than repeating it.

Android: check the schedule, not just the toggle

1. Go to Settings > Sound & vibration > Do Not Disturb > Schedules. Android treats each automatic schedule (Sleep, Work, or a custom one) as its own profile, and each can carry a different exception list than the one you set up manually. Checking the manual DND settings and assuming a scheduled one matches is the most common miss here.
2. Open the specific schedule that’s active overnight and check its Apps exceptions, not just whether “Alarms” is toggled on. The Alarms exception covers the alarm category the OS recognizes; a check-in or escalation notification from a third-party app is a separate notification, filed under Apps, and needs its own explicit allow.
3. Add the app under that schedule’s exceptions and set it to Priority or Unrestricted, depending on your Android version’s wording. Settings menus here vary enough by manufacturer that the exact label moves around, so look for anything combining “apps” and “exceptions” inside the schedule itself if the wording above doesn’t match exactly.

The actual test

Don’t just eyeball the settings. Put the phone into the Focus or DND state, trigger a real check-in or test notification from the app (most have a test-alert option in settings), and confirm it shows up immediately, not five minutes or five hours later. A setting that looks correct on screen and a notification that actually arrives on time are two different facts, and the gap between them is exactly what causes the “but I configured this already” complaints.

A second alarm source that never touches the phone’s notification settings at all sidesteps this whole category of misconfiguration, for better or worse depending on whether you actually want it to.