Should I Back Off With My Runs? Reading Post-Run Soreness vs. a Red Flag

"I used to run cross country in high school, so I'm no stranger to pushing myself hard — but I hadn't done much running in the last four and a half years. I recently started a weight-training course at university and added running as my cardio. I went out to see how far I could go, and covered 8 miles in about 70 minutes non-stop — the farthest I've ever run without stopping. The next day my legs, knees and hips were sore. Two days later, the soreness was gone. I weigh about 235 pounds, so I'm wondering: is this too much stress on my joints, or do I just need to keep pushing to build my muscles up?

– Stephen, Wisconsin

Answer by Dominique: Hi Stephen,
Thanks for your question about whether to back off after that soreness.

Soreness that builds over the day or two after an unusually long or hard effort and then fades within a few days (up to a week) is normal adaptation, not joint damage. What actually matters is how far past your recent normal the effort was, and whether you built up to it properly first — or, like you, jumped straight in after years off.

I'll break my response down as follows:

1. Normal Soreness vs. a Red Flag
2. Why the Jump Felt Like That: Distance, Body Weight, and a Long Layoff
3. A Safer Way Back In

1. Normal Soreness vs. a Red Flag

What you described sits squarely in normal-adaptation territory: sore the next day, no swelling, no pain during the run itself, and fully resolved within two days. That's a good sign, not a warning one.

A few things would flip that verdict, though. Watch for:

• Pain that keeps getting worse instead of easing after the first couple of days, or hasn't settled after about a week
• Swelling around the knee or hip
• Sharp, localised pain rather than a general ache
• Pain that shows up during the run itself, not just afterwards

Any one of those is a red flag. That's when you get it looked at by a professional — not when you push through and hope it settles on its own.

2. Why the Jump Felt Like That: Distance, Body Weight, and a Long Layoff

Three things stacked together to make that 8-mile run land the way it did.

First, the jump itself. Going from an unclear recent baseline straight to 8 miles non-stop in one session is a big jump — for anyone, whatever their history.

Second, body weight. At around 235 pounds, every step puts more ground-reaction load through your knees and hips than it would for a lighter runner. That's a reason to build mileage conservatively — it isn't a reason running is off the table. Current research doesn't back the idea that running itself damages healthy joints.

Third — and the one the original answer here missed entirely — your 4.5-year layoff. A high-school cross-country background leaves you with a mindset that's ready to push hard. But your aerobic fitness and connective-tissue conditioning dropped a long way over those years off, even though your effort tolerance didn't. That's the real driver here, and it's the piece a "the distance sounds a bit much" answer will always miss.

3. A Safer Way Back In

Here's what building back up properly actually looks like — not just "slowly," but with a number attached.

Start from a distance you can already repeat comfortably, not from that one all-out 8-mile effort, and increase it by around 10% a week from there. I've laid out the full progression rule, with a worked example, in my guide to building mileage using a safe progression rule.

Make this the core of your comeback — easy-paced, aerobic running that rebuilds the base your layoff took away.

One thing to leave out for now: interval running. Structured speed sessions aren't right for week one of a comeback. Save those until your base is properly back under you, not before.

If Your Situation Differs

A few related pages might fit better if the details differ from what you've described. If you're combining running with heavy training elsewhere, check the total running-plus-other-training load. If it's your whole weekly schedule that feels like a stretch, check whether your full schedule is too ambitious. And for the fuller research-backed answer on joints and distance running generally, see whether distance itself carries joint risk.

Since a multi-year layoff is the biggest factor in your case, returning after a long layoff changes the math — that page walks through the build-up itself in full.
So, Stephen — the soreness you had isn't a red flag. It's your body adjusting to a jump it wasn't ready for, made bigger by the layoff behind it. Build back up properly from here, using base running as your foundation and a sensible progression rule for mileage, and you won't be dealing with the same soreness each time.

All the best,
Dominique

Some Other Pages You May Like

Home > Running Training > Running Plateau > Should I Back Off With My Runs? Reading Post-Run Soreness vs. a Red Flag

  ☕ Buy Dom a Coffee