You followed the routine. Bath, books, low lights, drowsy-but-awake, and somehow — somehow — they actually went down at 7pm. You walked out of the room. You sat on the couch. You exhaled.

And then, somewhere between 7:35 and 7:50pm, the cry comes.

This is a false start, and it’s one of the most demoralizing things a baby’s sleep can throw at you. The crash is psychological. You’d already mentally clocked off. And the diagnosis is foggy because everything went right on the way down.

Here’s what’s actually happening, and the small set of fixes that work for most cases.

What a false start actually is

A false start is when your baby falls asleep at bedtime, wakes within 30 to 60 minutes, and is fully awake. Like a nap that ended, not a nighttime wakeup. They might be cheerful, fussy, or full-on crying, but the giveaway is that they don’t go back down with normal night-wakeup soothing.

Most false starts cluster between 30 and 60 minutes after sleep onset, around the length of one infant sleep cycle. Cycles run roughly 40 to 50 minutes for newborns and stretch to 50 to 60 minutes by 6 months. The wake-up is happening at the natural seam between cycles, when sleep is lightest. Most babies cross that seam and connect cycles. False-start babies don’t.

So the real question isn’t “why did they wake up at 7:45?” Almost every baby almost wakes at 7:45. The real question is why didn’t they fall back asleep on their own?

The four causes (roughly in the order they actually show up)

1. The last nap ended too late

This is the most common one, and the easiest to miss, because the bedtime routine itself looked fine.

Your baby builds up sleep pressure between waking and falling asleep. It’s what makes them tired enough to stay asleep, not just drift off and float back up twenty minutes later.

If the last nap ended at 5pm and bedtime is 7pm, you’ve only given them two hours to rebuild that pressure. Enough to fall asleep. Not always enough to stay asleep across the cycle hand-off. They drift out at the seam and can’t reconnect, because there’s not enough biological tiredness to push them back under.

The fix is either ending the last nap earlier or pushing bedtime later. Usually a 30-minute shift in either direction is enough.

2. Bedtime itself is too early

Sometimes the problem isn’t the last nap. It’s that bedtime has crept earlier than your baby’s body is ready for.

Sleep books love prescribing 7pm. Real babies care less about the clock and more about how long they’ve been awake. Bedtime also tends to creep earlier during a rough patch and then just stay there, because nobody remembers to push it back when the rough patch ends.

If your baby is bright-eyed and cheerful at the false-start wake — no crying, no fussing, just “hi, I’m up now” — bedtime is probably too early.

A quick test: shift bedtime 30 minutes later for three nights. If false starts disappear, you have your answer.

3. Overtired at the moment of going down

This is the opposite problem. Last nap was too short, last wake window stretched too long, and by the time they hit the crib, stress hormones have started to rise. They fall asleep fast (overtired babies often do, which is the trap), but the heightened arousal makes it harder to bridge the cycle seam, and they surface back up.

You’ll know it when you hear it. The cry is sharp, fast, and hard to settle. Not bright-eyed. Frantic.

The fix here is the inverse of the first one: get them down earlier next time, even if “earlier” feels too early. Better an overshoot than another night of overtired chaos.

4. Sleep cycle hand-off issues (the developmental one)

If the first three don’t fit, you might be dealing with a baby who hasn’t yet developed the skill of connecting sleep cycles independently. This is normal and usually self-resolves. It’s most common between 3 and 5 months as sleep architecture matures, and again around 8 to 10 months when the next regression hits.

Tracking when the false starts happen relative to bedtime can confirm it: if they’re hitting exactly 40 to 50 minutes after going down, every night, with no other obvious cause, you’re watching cycle hand-offs. Don’t change anything. Two to four weeks and they’re usually gone.

How to figure out which one is yours

Look at the cry, and look at the gap.

The cry tells you the hormonal state. Bright-eyed and cheerful means undertired or bedtime too early. Frantic and inconsolable means overtired. Whiny and confused, mid-volume, often means cycle hand-off.

The gap tells you about sleep pressure. Specifically: the time between when the last nap ended and when bedtime started. Many babies need a longer-than-textbook last wake window to build enough pressure for a clean bedtime. The textbook 2-hour gap at 6 months works for some babies and crushes others.

Once you start writing down the actual gap — not the routine, the gap — the pattern shows up fast. False-start nights almost always follow a last wake window that was shorter than your kid’s usual. The cause is upstream of the bedtime routine itself.

The two fixes that work for most false starts

If you do nothing else, do these two things:

Lengthen the last wake window by 15 to 30 minutes. Either cap the last nap earlier, or push bedtime back. Don’t change anything else for 5 nights and see what happens.

Track when false starts happen, not just whether they happen. A false start at 7:45 means something different than a wakeup at 9:30. The first is a cycle issue at the bedtime end. The second is closer to a true night wake-up that probably has a different cause.

That’s it. White noise, dark room, cooler temp, even sleep training. Those help sleep in general. They don’t fix false starts. Sleep pressure does.

When false starts mean something else

A few situations don’t follow the wake-window rules:

Illness or teething. A baby fighting an ear infection or pushing teeth will false-start regardless of timing. Drooling, ear-tugging, or appetite changes can point at one of these. Per AAP guidance, fever is not a normal teething sign and warrants a call to the pediatrician — don’t write it off as “she’s just teething.”
Sleep regressions (especially 4 and 8 months). The 4-month change is a permanent sleep-architecture shift, and it often shows up first as a wave of false starts. They tend to ease as the regression resolves.
Recently moved bedtime. Any shift more than 20 to 30 minutes from the old bedtime can take roughly a week to settle. Don’t diagnose a false start until you’ve held the new time for several nights.

The 7-day experiment

Pick whichever cause sounds most like your kid, change one thing, hold it for seven nights. Don’t tweak. One night tells you nothing — sleep is too noisy. A week is the smallest unit that means anything.

Each night, write down (or log):

Time the last nap ended
Time bedtime started
Whether a false start happened
If yes, what time

If false starts drop or disappear, you found your cause. If not, change one variable for the next seven nights.

This is the part of bedtime that breaks you when you’re already not sleeping. Keeping track of the gap. Doing the math at 7pm. Remembering what you tried last Tuesday.

We built Robin Baby’s sleep forecast partly because of this exact problem. It pulls from your last 14 days of logged naps and bedtimes, computes what your baby’s actual wake windows have been (not the textbook ones), and tells you when bedtime should be tonight based on when the last nap actually ended today. You stop doing the bedtime math at 7pm.

The sleep forecast is free, no subscription. It’s the feature parents need most when they’re already running on fumes.

The honest bottom line

Most false starts are a sleep-pressure problem, not a sleep-skills problem. Before you consider sleep training, dropping a nap, or any of the bigger interventions, try a 30-minute wake window adjustment first. Highest-yield change for the lowest cost. Most parents solve it within a week.

If it doesn’t, the cause is usually identifiable from the timing pattern, and the longer-term fix follows from there.

You’re not doing anything wrong. False starts are the kind of problem that looks like a routine failure but is almost always a clock problem.

False starts at bedtime: why your baby wakes 30 minutes after going down