There are two versions of this morning. In the first, you wake up late, grab your phone, and see your alarm sitting there switched off — but you have no memory of touching it. In the second, you wake up late and the alarm is still switched on, still set for the right time, and it just... never made a sound.
Those are completely different problems, and people constantly waste time solving the wrong one. This post is about the second version: the alarm that genuinely didn't fire. It's almost never a broken phone. It's almost always a setting, and it's usually one of about seven.
Here's the order I check them in, fastest first.
Start By Working Out Which Failure You Had
Before you change anything, open the Clock app and look at the alarm in question. Is its toggle still on or off?
If it's off, the alarm probably did ring and something turned it off — most likely you, in the fog of sleep inertia, with no memory of it afterwards. That's a behavioural problem, not a technical one, and I've written about why your brain dismisses alarms without waking you separately. No amount of settings-fiddling fixes that one.
If it's still on, and it's a non-repeating alarm, that's suspicious in itself: a one-off alarm switches itself off after it rings. An alarm that's still armed the morning after usually means it never fired. Keep reading.
Check 1: The Alarm Was Never Actually Armed
The dumbest cause, and the most common. You opened the Clock app, tapped the plus button, set a time, and then walked away without hitting Save — or you edited an existing alarm and backed out instead of confirming. Either way, nothing was scheduled.
The related trap: you set a new alarm for 6:30, but the old 6:30 alarm from three months ago is the one you'd previously switched off, and you're now looking at the wrong row in a list of nine alarms. If your alarm list is a graveyard of half-forgotten times, delete everything you don't use. A list with two alarms in it is a list you can actually verify at a glance.
Check 2: AM Versus PM
I've done this. You set 6:30 for the morning and the picker was sitting on PM. The alarm was armed, correctly, for the evening — it just fired twelve hours after you needed it.
This one is easy to miss because the AM/PM column is small and the hour looks right. If you can, switch your phone to a 24-hour clock in the date and time settings. It removes the entire category of mistake, permanently.
Check 3: The Repeat Schedule Doesn't Include Today
This is the one that produces the maddening "it works some days but not others" pattern.
Open the alarm and look at Repeat. If it's set to weekdays and today is Saturday, the alarm will not ring, and there's nothing wrong with your phone. If it's set to Never, it fires once and switches itself off — which is fine until the week you assume it's still running.
The nastiest version is a repeat schedule you set up ages ago and forgot about: Monday, Wednesday, Friday from a gym phase you abandoned. Everything looks armed. It's just not armed for today.
Check 4: You Edited the Sleep Alarm, Not the Clock Alarm
This trips up a huge number of people. On modern iPhones there are effectively two kinds of wake-up alarm: a normal alarm you create in the Clock app, and the wake-up alarm attached to your Sleep Schedule, which is managed through the Health app and shown separately in the Clock app.
They are not the same alarm, and editing one does nothing to the other. So you "change your alarm to 7:00", the change lands on the Clock alarm, and your sleep schedule keeps quietly doing its own thing — or vice versa. Sometimes both fire. Sometimes neither does what you expected.
If your Clock app shows a separate sleep or wake-up section above your alarm list, you have both systems running. I go into detail on untangling them in the Sleep Focus and Sleep Schedule post, but the short version: decide which one you're using, and turn the other off completely.
Check 5: Do Not Disturb and Focus Modes
Let's clear this up, because it's the first thing everyone blames: Clock app alarms are designed to ring through Do Not Disturb and Focus modes. A Focus mode by itself does not silence your alarm.
Where Focus does cause trouble is indirectly. A scheduled Focus can be tied to a Sleep Schedule whose wake-up alarm you've since disabled, so the Focus turns on at night and nothing turns on in the morning. Custom Focus modes can also be set to trigger on a schedule you no longer remember creating. And if you're relying on a third-party alarm app rather than the Clock app, notification and Focus settings matter a lot more, because that app is delivering through the notification system.
So: check your Focus schedules, but don't expect turning Do Not Disturb off to be the fix. It rarely is.
Check 6: Screen Time and Downtime
If you use Screen Time, look at Downtime and App Limits. Downtime doesn't touch Clock app alarms, but it can block third-party apps from being opened during the hours you've set — which is a real problem if your alarm app needs to be launched to complete a dismissal task, or if you've limited a category that includes it.
Add any alarm app to your always-allowed list. It costs nothing and removes a genuinely confusing failure mode.
Check 7: Volume, Speaker, and Headphones
An alarm can fire correctly and still produce almost no sound. The alarm volume on an iPhone lives in the sound settings as the ringer and alerts level, and it isn't necessarily what your volume buttons are adjusting. On top of that, a case that covers the speaker, dust in the speaker grille, or connected AirPods can send the sound somewhere you can't hear it.
That's a big enough topic that I split it out: see why your iPhone alarm is too quiet and what happens when AirPods are connected. If the alarm was faint rather than absent, start there.
The Two-Minute Test That Ends the Guesswork
Whatever you change, verify it the same way: set an alarm for two minutes from now, put the phone down, and wait. Don't reason about it. Watch it fire.
Do this test with your phone in the exact state it'll be in overnight — same volume, same case, same silent switch position, same AirPods situation, same Focus mode. Half the alarm problems I've helped people with survived a "check the settings" pass and died instantly on a live test.
When the Settings Are Fine and You're Still Late
Here's the uncomfortable part. Once you've been through all of this, most people discover the alarm was firing all along. The phone did its job. Something in the first ten seconds of consciousness swiped it away.
That's the failure I couldn't fix with settings, and it's why I stopped using the Clock app as my primary alarm. I use Captain Wake instead, because its alarm doesn't have a swipe-to-dismiss at all. It ends when you complete a mission — photograph a specific object, scan a barcode you left in the kitchen, solve a few math problems, shake or spin the phone. The alarm re-arms itself through app kills, phone restarts and silent mode, the volume escalates the longer you ignore it, and snooze is capped at a single five-minute round so you can't ride it for an hour.
Settings problems are worth fixing — a misconfigured alarm is a guaranteed failure. But once they're fixed, the remaining question isn't whether your alarm rings. It's whether you're still in bed when it stops.
