Warning Signs You're Returning to Running Too Fast (And What to Do About Them)

Normal comeback soreness fades within a day or two and doesn't get worse session to session. A warning sign is pain that lingers past 24 hours, swelling or warmth that doesn't settle, or a pace you're chasing because you used to run it — not because your body has earned it back yet. That's the test. Below, I'll walk you through exactly what to do about each one, sign by sign.

Why Comebacks Carry a Different Injury Risk Than Normal Training

Most overtraining advice out there is written for runners whose tissue is already adapted to the load — established runners whose tendons and bone have long since caught up with their training. You're not that runner right now.

Your comeback sits in a different risk window: the weeks to few months where your cardiovascular fitness has already outpaced what your tendons and bones have adapted to carry. That's exactly why this window is when warning signs matter most — and when they're easiest to miss, because feeling fit is genuinely misleading here.

If you haven't already, read the general break-length return framework first. This page is the week-to-week self-check that sits on top of that plan, not a second copy of it.

The Cardio-vs-Tissue Mismatch: Why You Feel Ready Before You Are

Here's the mechanism in one paragraph, because the rest of this page only makes sense once you've got it. Your cardiovascular fitness and how easy a run feels improve within roughly two to three weeks of consistent running — well before your tendons and bone have finished their own, much slower adaptation timeline. A comfortable heart rate and easy breathing are not evidence that your tendons and bones are equally ready. They're evidence that one system has caught up. Not all three.

For the full mechanism — plus how age and break length change the timeline — see why your fitness returns faster than tendon and bone.

Normal Adaptation Soreness vs. a Genuine Red Flag

Location and trajectory — not how sore you feel in the moment — are the real test here. Here's the direct contrast:

Normal Adaptation Soreness Genuine Red Flag
General muscle fatigue or mild stiffnessPain localised to a single joint or tendon, not general muscle fatigue
Peaks within 24-48 hoursGets worse rather than better, day over day
Eases with light movementAny swelling or warmth that doesn't settle
Symmetric — affects both legs similarlyPain that changes your gait

The pattern I see most often with comeback athletes: they track pain intensity carefully, but rarely track pain trajectory — and trajectory is actually the more reliable signal. A 2/10 that's still a 2/10 on day three is a very different situation to a 2/10 that was a 1/10 yesterday.

Physical Warning Signs to Track: Pain, Swelling, Stiffness, and Resting Heart Rate

No ranking page consolidates this list in one place, so here it is. Track these five signals, and treat each one as a checkable threshold rather than a vague feeling:

  • Pain scale: running pain above roughly 2-3/10, or pain that climbs by 2/10 or more mid-run, is a stop signal.
  • Swelling or warmth: any that lingers past the end of a run, rather than settling within minutes.
  • Stiffness: stiffness that doesn't loosen within the first kilometre of an easy run.
  • Resting heart rate: an elevation of several beats per minute above your normal baseline, sustained across multiple mornings.
  • Sleep: disrupted sleep alongside any of the above — on its own it's a nudge, alongside a physical sign it's confirmation.
Beware treating any one of these in isolation. It's the combination — and the trend over several days — that tells you what's actually going on, not a single bad morning.

The "Chasing Old Paces" Trap: Psychological Warning Signs

Here's a trap that rarely makes it onto any warning-signs list, and it's arguably the one I see most often: judging a comeback run against a pace or split time you hit before your break, instead of against how the effort actually feels right now.

Ask yourself two questions mid-run. Would this pace feel easy if you hadn't run it before? And are you speeding up because the workout calls for it, or because a number on your watch is bothering you? If you hesitate on either, you're chasing.

The consequence is predictable. The run-walk structure or easy-day plan your break-length schedule calls for gets quietly skipped, because a pace felt "achievable." Achievable and appropriate are not the same thing.

I coached a masters athlete back from a multi-month break who kept nudging their easy runs toward an old marathon-pace effort, because — in their words — "it felt fine." What they hadn't connected was three weeks of unusually elevated resting heart rate running alongside it. The psychological trap and the objective-monitoring gap were compounding each other, and neither one had raised a flag on its own until I pointed it out.

What to Do When a Warning Sign Shows Up: A Simple Decision Tree

Once you've spotted a sign, the question is simple: what do you actually do about it? Here's the decision tree I use with the runners I coach through a comeback:

Warning Sign What to Do
Mild soreness that eases within 48 hoursContinue as planned
Pain during a run, under the 2-3/10 thresholdHold at your current mileage for the week
Pain at or above the threshold, or pain that increases mid-runCut mileage by roughly 20-30% and reassess in 3-4 days
Any swelling, warmth, or a change in your gaitStop running and reassess with a professional or the injury-specific page below
Sustained resting-heart-rate elevationCut mileage by roughly 20-30% and reassess in 3-4 days
The "chasing paces" catchHold at your current mileage for the week, and deliberately slow to the prescribed easy effort

The specific numbers here matter, and they're the standard I apply with returning athletes: a 20-30% cutback, held for a minimum of 3-4 days before you reassess — not just until the next run happens to feel okay. Reassessing too early is how a genuine cutback quietly turns into no cutback at all.

To match a cutback to your actual break length rather than a generic number, adjust your mileage cutback to your break-length schedule. If you're coming back from two months or more off, the longer-timeline plan if you're returning from 2+ months off is worth reading in full — the numbers there are more conservative for good reason.

When to Stop Self-Managing and See a Professional

Self-monitoring has a limit, and knowing where it sits matters as much as the checklist itself. See a physio or doctor rather than continuing to self-manage if:

  • A warning sign from the decision tree above doesn't resolve after the recommended cutback and reassessment window.
  • The pain changes character — it turns sharp, localised, or worse, rather than staying diffuse and easing.
  • Any sign pairs with a specific suspected injury, such as a stress fracture or a tendon issue.
  • You've cut back repeatedly over several weeks with no sustained progress to show for it.
Any one of those means: get assessed. Everything short of that means: keep self-monitoring, and keep applying the decision tree above.

Once you or a professional has identified a likely cause, injury-specific pain-scale and loading rules covers the frameworks for training around it properly.

Frequently Asked Questions

How is comeback soreness different from an injury warning sign?

Normal comeback soreness peaks within 24-48 hours, eases with light movement, and affects your muscles generally rather than one joint or tendon. A warning sign gets worse rather than better, sits in one specific spot, or comes with swelling or warmth.

What pain level means I should stop a run immediately during a comeback?

Pain at or above roughly 2-3 out of 10, or pain that climbs by 2/10 or more partway through a run, is a stop signal rather than something to push through.

Is it normal for a returning run to leave me sore for a couple of days?

Yes — general muscle soreness lasting up to about 48 hours is typical adaptation. Soreness that persists longer than that, or worsens day over day, is not.

What does it mean if swelling or warmth lingers after a run?

Lingering swelling or warmth around a joint or tendon is a tissue-level red flag, not ordinary training fatigue. It warrants cutting your mileage and reassessing, not continuing the plan as written.

How do I know if I'm chasing my old paces too soon?

If you're judging a run against a pre-break split rather than how the effort feels, or speeding up because a number bothered you rather than because the workout called for it, you're chasing paces before your tissue has caught up to your cardio fitness.

Should I use resting heart rate to monitor my comeback progress?

Yes. A resting heart rate elevated several beats per minute above your normal baseline across several consecutive mornings, especially alongside disrupted sleep, is a useful early objective warning sign alongside how you feel.

What's the difference between a down day and a sign I need to actually cut my plan back?

A down day is a single off session with no lingering pain or swelling by your next run. A sign to cut back is a pattern — repeated soreness, a rising resting heart rate, or pain that doesn't fully resolve between sessions.

If I get a warning sign, how much should I cut my mileage or take off?

For most mid-range signs, cutting mileage by roughly 20-30% and reassessing in 3-4 days is a reasonable default. A pain-scale or gait-change red flag warrants stopping running entirely rather than just reducing volume — see the decision tree above.

When should I see a physio or doctor instead of just backing off on my own?

If a warning sign doesn't resolve after a cutback and reassessment window, changes character to sharp or localised pain, or you've cut back repeatedly over several weeks with no sustained progress, it's time to get assessed rather than keep self-managing.


None of this is a reason to run scared through your comeback. It's a reason to be precise about it — know which sensation to shrug off, and which one to actually act on. Get that right, and this comeback will be a lot shorter than the one you're trying to avoid.

Some Other Pages You May Like


The Science of Detraining Returning to Running After a Long Break Return-to-Running Schedules by Break Length Returning to Running After an Injury Tired Legs After Running? Speed Training Readiness Checklist Should I Back Off With My Runs? Reading Post-Run Soreness vs. a Red Flag Marathon Training Tips


Home > Running Training > Return to Running After Time Off > Warning Signs You're Returning Too Fast

About the author

Dominique de Rooij

Dominique de Rooij (Dom)

Advanced Running Coach certified by Athletics Australia with 20 years of writing about running and over a decade coaching runners — from first-timers to marathoners. Dom's beginner programs have guided thousands of runners and been praised above plans from Jeff Galloway, Hal Higdon, and Runner's World. Now over 50, Dom still loves trail running, parkrun, and the coffee after.




What's New?

  1. Personalized Running Coaching - BRT | Run Smarter, Race Better

    Get a personalized running program built around your current fitness, goals, and schedule - not a generic app template. Choose from BRT Silver, Gold, or Platinum coaching with Dom, accredited running…

    Read more

  2. Sample 4-Day Marathon Training Week: Base to Taper

    A full 4-day-a-week marathon training schedule, phase by phase - base, build, peak, and taper - with named workouts and weekly mileage.

    Read more

  3. Marathon Taper for a 10-12 Week Training Cycle

    How to taper correctly on a compressed 10-12 week marathon plan - the right taper length, why standard advice doesn't fit, and the week-by-week structure.

    Read more


More New Posts →