Why Didn't My iPhone Alarm Go Off?

6:52am. Alarm was set for 6:15. Phone’s right there, screen dark, a little crescent-moon icon sitting in the status bar. Obvious conclusion: Focus Mode ate the alarm.

It almost certainly didn’t. Apple built Focus modes, Sleep Focus included, to let alarms set in the Clock app ring at full volume no matter what’s silenced. That’s been true since Focus modes launched, and it still holds. If your alarm stayed quiet, one of six other things is the actual reason, and it’s worth checking them in this order.

1. The ringer switch and the alarm volume slider

Not the same as your ringtone volume. Go to Settings > Sounds & Haptics and look at the slider under “Ringer and Alerts.” If it got dragged to zero, alarms go with it. Also flip the physical mute switch on the side of the phone; it’s easy to bump in a bag or a pocket overnight.

2. Audio routing

If AirPods were charging nearby, or the phone was still paired to a car or a Bluetooth speaker from the drive home, the alarm sound may have played somewhere you weren’t. Check Control Center’s audio card before bed instead of after the fact — it’s one of six device-level checks worth running before assuming an alarm failure means something bigger, on any phone, not just iPhones with Focus Mode involved.

3. The Health app’s Sleep Schedule

This is the actual source of most of the confusion people blame on Focus. Set a sleep schedule under Health > Sleep and iOS builds its own “Wake Up” alarm, a gentler tone that ranks near the bottom of independent testing on which alarm sounds actually rouse heavy sleepers. That alarm can run in place of, or alongside, whatever’s sitting in the Clock app, and it’s easy to forget it exists.

4. Time Sensitive Notifications for third-party apps

Apple’s built-in alarm exemption used to cover the Clock app only, with everything else depending on notification permissions instead. That changed with AlarmKit, the framework Apple opened up to developers in iOS 26: an app built on it gets the same automatic Focus-bypass as Clock, no permission toggle required. Not every alarm app has adopted it yet. For the ones that haven’t, the old rule still applies — if Time Sensitive Notifications is off inside that app’s settings, or the app isn’t listed under Settings > Focus > [your Focus] > Apps, a Focus mode can legitimately silence it. Check which category yours falls into before assuming a permissions fix is even necessary; a rundown of how four popular alarm apps behave once you actually miss one covers the gap between them, and a deeper technical breakdown of why AlarmKit exists and what it still doesn’t cover is worth reading if step 4 is the one that actually applied to you.

5. Whether the alarm is even on

Open Clock > Alarms and check the toggle itself. A half-finished edit (changed the time, forgot to re-enable it) looks exactly like a Focus problem from across the room.

6. Restart the phone

Apple has quietly acknowledged alarm bugs in past iOS releases where a correctly configured alarm just doesn’t fire. If steps 1 through 5 all check out and it still happened, a restart before bed is the boring fix that actually works.

Note: If this keeps happening, the real fix is a second layer, not another settings audit. DontSnooze requires an actual recorded response to prove you’re up — the same automatic-consequence mechanic that makes half-asleep dismissals harder to fake — so a Focus misconfiguration doesn’t get the final say on whether you woke up.

Run through steps 1 through 4 tonight, before the next alarm is due. Checking them at 6:52am, already late, is a much worse position to be checking from.