5 Warning Signs in Your Watch Data That Predict Race-Day Fueling Disaster

Your Garmin or Apple Watch has been collecting data for months. You've tracked every long run, every tempo session, every easy recovery jog. You can see your pace, your heart rate, your training load, your sleep.

But here's what most runners don't realise: that data is already telling you whether your race-day fueling plan is going to work — or fall apart.

The signs are there. Most runners just don't know what to look for.

With fall marathon season weeks away, now is the time to open your watch app and look for these five warning signs. Each one predicts a specific race-day problem — bonking, cramping, GI distress, or hitting the wall — and each one can be fixed before you toe the start line.

1. Heart Rate Drift on Long Runs — The Dehydration Alarm

Heart rate drift is when your heart rate climbs during a steady-effort run, even though your pace stays the same. If you ran the first 5 miles of your last long run at 145 bpm and the last 5 miles at 160 bpm — same pace, same perceived effort — that's drift.

Your watch tracks this automatically. Garmin shows it in the heart rate graph of any recorded activity. Apple Watch records it in every workout. Most runners glance at their average heart rate and move on. That's a mistake.

What it predicts: Heart rate drift beyond 10–15 beats over a long run is a reliable signal that you're losing more fluid than you're replacing. As blood volume drops from sweat loss, your heart has to beat faster to deliver the same amount of oxygen. The technical term is cardiovascular drift, and it's directly proportional to your fluid deficit.

Why it matters for race day: If your long runs consistently show drift above 15 bpm, your hydration plan isn't keeping up with your sweat rate. On race day, that same drift will compound over 26.2 miles — your body will redirect blood away from your gut to keep your muscles supplied, slowing digestion. That means the gels you take after mile 16 won't absorb properly, and you'll bonk despite technically fueling on schedule.

What to do now: Go back through your last four long runs in your watch app. Note the heart rate at miles 3–4 (after warm-up) and compare it to the heart rate at the same pace in the final 3–4 miles. If the gap is consistently above 15 bpm, you need to increase your fluid intake during those runs — and carry that higher intake into your race-day plan.

Sweatr reads your heart rate data from every long run and cross-references it with temperature, humidity, and your personal sweat rate to detect drift patterns automatically. When drift trends upward across multiple sessions, it adjusts your hydration targets before the next run — not after you've already had a bad one.

2. Calorie Burn Spikes Without Matching Intake — The Glycogen Debt Signal

Your watch estimates calories burned in every workout. Those numbers aren't perfect — Garmin has been shown to underestimate by 17–40% in some conditions — but the trend is what matters.

Look at your training load over the past 4–6 weeks. If you had a week where your total calorie burn jumped significantly — a big week of training, a heat wave that spiked your effort, or back-to-back long sessions — that's a glycogen debt signal.

What it predicts: When your training load spikes and your eating doesn't match, you accumulate a calorie and glycogen deficit. Your body draws down its carbohydrate reserves, and if you don't fully replenish them before race day, you'll start the marathon with a smaller fuel tank than you think. This is one of the most common hidden causes of bonking — athletes who "did everything right" on race morning but were already in debt from a hard training week.

Why it matters for race day: A glycogen debt from three weeks ago can take days to fully recover if you're still training through it. If your watch shows a major training load spike in the past month and your weight dropped during that period, your carbohydrate stores may still be catching up.

What to do now: Open your watch's training load or weekly summary view. Flag any week where estimated calorie burn was 20% or more above your 4-week average. Then ask yourself: did you eat more that week to compensate? If you can't remember, you probably didn't. In the remaining weeks before your race, prioritise consistent carbohydrate intake — not just carb loading in the final 48 hours — to refill the tank completely.

Sweatr tracks your cumulative energy balance across your entire training block, not just individual workouts. It flags when your calorie output outpaces your intake over multiple days and recommends specific recovery nutrition targets to close the gap before race week.

3. Resting Heart Rate Creeping Up — The Overtraining and Under-Recovery Signal

Your watch tracks resting heart rate every night. It's one of the most reliable signals your body produces, and most runners check it occasionally but don't track the trend.

A rising resting heart rate over 2–3 weeks, even by 3–5 beats per minute, is a sign that your body isn't recovering between sessions. The causes can be training load, poor sleep, stress, illness, or — and this is the one most athletes miss — inadequate fueling.

What it predicts: A rising resting heart rate heading into taper is a red flag for two race-day problems. First, your body is entering race week already fatigued, which means your glycogen storage capacity is compromised. Fatigued muscles store less glycogen. Second, elevated sympathetic nervous system activity (what's driving the higher resting HR) also affects gastric motility — your gut doesn't work as well when your body is stressed.

Why it matters for race day: Runners who arrive at the start line with a resting heart rate 5+ bpm above their baseline are more likely to experience both bonking and GI distress. Their fuel tank is smaller and their digestion is slower — a double hit.

What to do now: Look at your resting heart rate trend over the past 3 weeks. If it's trending up, the fix isn't just more rest — it's also more fuel. Under-recovered athletes often need 200–400 additional calories per day, predominantly from carbohydrates, to support their training load. Taper alone won't fix a calorie deficit; you need to eat into it.

Sweatr monitors your resting heart rate trend alongside your training load and flags under-recovery patterns. When it detects a rising resting HR with high training load, it recommends increased carbohydrate intake on recovery days — because the problem isn't just training too much; it's eating too little to support what you're doing.

4. Sleep Score Drops in the Final Training Block — The Gut Distress Predictor

Garmin, Apple Watch, and most modern wearables now score your sleep quality nightly. Body Battery, Sleep Score, Sleep Stages — the labels differ, but they all measure the same thing: how well you recovered overnight.

Most runners treat sleep scores as interesting but not actionable. That's a mistake heading into race week.

What it predicts: Poor sleep in the 7–10 days before a race is one of the strongest predictors of race-day GI distress. The gut-brain axis is real: stress hormones released during poor sleep increase intestinal permeability and slow gastric emptying. Two or three nights of genuinely poor sleep can measurably change how your gut handles carbohydrates during exercise.

This is separate from the "I always sleep badly the night before a race" phenomenon — one bad night has minimal impact on performance. But a pattern of poor sleep during your peak training block compounds.

Why it matters for race day: If your sleep scores have been trending down for 2–3 weeks, your gut is less prepared to handle the carbohydrate load you're planning to throw at it during the race. The gels that worked fine in training may cause nausea, bloating, or worse on race morning — not because the products changed, but because your gut's ability to process them did.

What to do now: Review your sleep data for the past two weeks. If your sleep score has dropped by 10% or more from your baseline, address it now — not the night before the race. Prioritise sleep hygiene: consistent bedtime, reduced screen time, cooler room temperature, and reduced caffeine after midday. And on the nutrition side, consider reducing the concentration of your race-day carb intake (more sips of diluted drink mix, fewer concentrated gels) to ease the load on a stressed gut.

Sweatr factors your sleep quality data into every fueling recommendation. On days when your watch reports poor sleep, Sweatr adjusts your training nutrition — slightly more frequent, smaller doses of carbohydrate — to match what your gut can actually handle that day.

5. Consistent Weight Loss Across Long Runs — The Sweat Rate Mismatch

This one requires a bathroom scale, not just your watch — but your watch provides the context that makes the number meaningful.

If you're weighing yourself before and after long runs (you should be), and you're consistently losing more than 2% of your body weight during those sessions, your hydration plan has a leak.

What it predicts: A 2% body weight loss during exercise corresponds to roughly 1–1.5 litres of unreplaced fluid for a 70kg runner. At that level, blood volume drops enough to measurably reduce cardiac output, raise core temperature, and — critically — reduce blood flow to the gut.

The math is straightforward: if you lose 1.5kg during a 2-hour long run, your sweat rate is approximately 750ml/hour (adjusting for any fluid consumed). If you only drank 400ml/hour during that run, you're running a 350ml/hour deficit. Over a 4-hour marathon, that's 1.4 litres of unreplaced fluid — enough to shut down gastric absorption in the final third of the race.

Why it matters for race day: This is the most common reason gels "stop working" after mile 18. It's not that your body ran out of capacity to absorb carbohydrate. It's that dehydration reduced blood flow to your gut, so the gel you swallowed is sitting in your stomach instead of reaching your bloodstream. You feel nauseous, you stop fueling, and you bonk — even though you have unused gels in your pocket.

What to do now: Weigh yourself before and after your next two long runs, nude, after towelling off. Record how much fluid you consumed during the run. Calculate your sweat rate: (pre-run weight minus post-run weight in kg, plus litres consumed) divided by hours run. That's your hourly sweat rate. Your hydration plan should replace 70–80% of that number — not 100%, but not 50% either.

If you've been running a significant deficit on every long run, you need to practise drinking more during your remaining training sessions. Your race-day plan should include a specific millilitre target per aid station, not just "drink when thirsty."

Sweatr calculates your personal sweat rate from your wearable data and historical weight-loss patterns. It sets a precise hourly fluid target — not a range, a number — and adjusts it for the forecast temperature on race day. No bathroom-scale math required.

The Pattern That Matters

Any one of these signals in isolation might be noise. A single bad night's sleep, one long run with heart rate drift, one week of heavy training — these happen in every training block.

But when two or three of these signals appear together, they form a pattern that almost always predicts race-day trouble. Heart rate drift plus rising resting HR plus weight loss on long runs is a hydration problem. Sleep score drops plus calorie burn spikes plus resting HR creep is an under-recovery and under-fueling problem.

Your watch is already collecting all of this data. The question is whether you're reading it — and acting on it — before race day.

Stop Reading Data. Start Using It.

Most runners use their watch to record what happened. But the real power of wearable data is predicting what's about to happen — and changing it before it does.

That's what Sweatr was built to do. It connects to your Garmin, Apple Watch, or Strava, reads your training data, and builds a personalised fueling and hydration plan based on your actual numbers — your sweat rate, your training load, your sleep quality, your heart rate patterns. Not generic ranges. Your numbers.

If any of the warning signs in this article looked familiar when you checked your data, Sweatr can tell you exactly what to change — and build the plan that accounts for what your watch is already telling you.

Your fall marathon is weeks away. Your watch has the data. Now use it.