Skip to content
Train Ultra
← All posts
Training Decisions 11 min read

When Soreness Is Normal, and When It Is a Warning Sign

When Soreness Is Normal, and When It Is a Warning Sign editorial image for Train Ultra.

Soreness is part of ultramarathon training, especially after long descents, hill blocks, strength work, or any session your legs were not quite ready for. The problem is that soreness and injury do not announce themselves with clean labels. Many runners ignore something that needed caution, while others panic over a normal training response and shut down a week that could have continued just fine.

The useful question is not, “Am I sore?” It is, “What kind of soreness is this, and what should I do with tomorrow’s training?” That matters because ultrarunning rewards consistency far more than single heroic sessions. A smart decision on day two or day three after a hard effort often matters more than the workout that made you sore in the first place.

Most normal post-training soreness is delayed onset muscle soreness, often called DOMS. Sports medicine references and the American College of Sports Medicine describe it as soreness that usually begins several hours after exercise, builds over the next day or two, and settles within a few days. It is especially common after eccentric loading, which is exactly what happens in downhill running and some forms of strength training. Your quads feel tender, stiff, or heavy. Stairs become a negotiation. The muscles are diffusely sore when you press on them or start moving, then often loosen slightly once you warm up.

That pattern is uncomfortable, but it is usually not dangerous. It means the training created more muscular disruption than your body was recently used to. In ultrarunners, the classic triggers are a first big vert week, a downhill-heavy long run, a return to lifting, or a faster session after a long stretch of mostly easy volume.

Warning-sign pain tends to look different. It is more likely to be sharp, localized, asymmetrical, and mechanically specific. Instead of both quads feeling wrecked after a mountain long run, maybe one spot at the top of your calf hurts every time you push off. Instead of general glute soreness after hill reps, maybe you feel a pinch deep in one hip with each stride. Instead of stiffness that improves after ten to fifteen minutes, maybe the pain gets worse as the run goes on, changes your gait, or is still noticeable at rest.

A simple first screen is this: normal soreness is broad and predictable, warning-sign pain is specific and behavior-changing.

Signals that usually point to normal soreness

Normal soreness usually has a story that makes sense. You did something harder, steeper, longer, or newer than usual. The soreness showed up later that day or the next morning. It affects the muscles you would expect. Both quads after technical descents. Calves after uphill treadmill work. Glutes after heavier split squats. The discomfort is dull, stiff, tight, or achy rather than sharp.

It also tends to improve as your body warms up. The first mile may feel rough, but an easy shuffle often turns the volume down. That does not mean you should force a hard workout through sore legs. It means the tissue is acting like tired muscle, not like something that is failing under load.

Another sign is symmetry. Training stress usually hits patterns, not random isolated points. If both calves are sore after a hilly long run, that is usually less concerning than one small painful area in one calf. Symmetry is not a guarantee of safety, but it is helpful context.

Time course matters too. DOMS usually peaks around one to two days after the provoking session and then fades. If the soreness is clearly getting better each day, that is reassuring. If it is still just as severe on day five, or if it is spreading, intensifying, or changing character, the odds shift.

Signals that deserve more caution

Pain deserves more respect when it changes how you move, when it is easy to point to with one finger, or when it keeps building once you start running. A sore set of quads that makes stairs awkward is one thing. A pain in the shin that gets sharper each minute is another.

These are the signs that should slow you down and often change the next training decision:

  • Pain that is sharp, stabbing, or catches with a specific movement.
  • Pain in a tendon, bone, joint, or one small spot rather than across a muscle group.
  • Swelling, redness, bruising, or warmth.
  • Limping or any visible change in form.
  • Pain that worsens during the run instead of easing slightly with warm-up.
  • Pain at rest, pain that wakes you at night, or pain with normal walking.
  • Symptoms that persist beyond several days without meaningful improvement.

Bone stress problems and tendon irritation often begin as something runners try to rationalize away because the early discomfort can seem manageable. What matters is not whether you can still run through it today. What matters is whether the pattern says the tissue is tolerating load poorly. If pain becomes more focal, more repeatable, and more sensitive to impact, that is not a “tough it out” situation.

Why ultrarunners get this wrong

Ultrarunners are unusually good at normalizing discomfort. That is useful in races and sometimes useful in training, but it can blur the line between adaptation and warning. Many runners also make the decision too early. They wake up sore, panic, and scrap the week, or they wake up sore, insist everything is fine, and force the exact session on the plan.

Neither approach is very good. Soreness is a data point, not a verdict.

The better move is to ask four questions.

A practical decision framework

1. Does the soreness match the training you did?

Start with the obvious. If you are sore in places that fit the session, that lowers the concern. Downhill race simulation followed by quad soreness makes sense. Heavy calf raises followed by calf soreness makes sense. Random pain on the outside of one knee after an otherwise ordinary easy run deserves more suspicion.

When soreness has no clear training explanation, be more conservative.

2. Is it diffuse muscle soreness, or focal pain?

Diffuse soreness across a muscle group is usually more compatible with normal training damage. Focal pain in a small area raises the likelihood of strain, tendon irritation, or bone stress.

This is one of the most useful distinctions a runner can make. “My hamstrings are sore” is different from “there is one exact point high on my hamstring that hurts when I lengthen my stride.” The second description should change your decision.

3. What happens after ten to fifteen minutes of easy movement?

A short easy warm-up is often informative. Normal soreness often softens once blood flow increases and joints start moving. Warning-sign pain often stays the same or becomes more obvious as the stride repeats.

This is not a license to test severe pain with a run. It is a way to evaluate mild to moderate symptoms that are not clearly alarming. If you start easy and the discomfort ramps up, alters mechanics, or makes you protect one side, stop and change the day.

4. What is the trend over 48 to 72 hours?

Single snapshots can mislead. Trends matter more. If soreness is easing, range of motion is returning, and normal walking feels better, you are probably moving in the right direction. If pain is becoming more localized, your easy pace is dropping for the same effort, or your gait still feels guarded, treat that as accumulating evidence.

If your easy running has also felt off lately, the decision may fit into a bigger recovery picture than soreness alone. In that case, it helps to think through the broader patterns discussed in why your easy pace suddenly got slower.

What to do next, based on what you find

If the soreness looks and behaves like normal DOMS, you usually do not need full rest. Light movement is often better than complete shutdown. Easy running, walking, or low-intensity spinning can help you feel less stiff, even if it does not magically speed tissue repair. What you should usually avoid is stacking another high-force session on top of tissue that is still notably damaged.

That means if Tuesday’s downhill long run wrecked your quads, Wednesday can still be an easy aerobic day, but Wednesday is probably not the best time for steep hill sprints or a hard tempo on tired legs. You are not losing fitness by making that swap. You are protecting consistency.

If the pain looks suspicious, the first decision is simpler. Reduce or remove impact until the pattern is clearer. That may mean replacing a run with easy cycling, shortening the session to a walk-jog test that you stop at the first sign of worsening, or taking a full day off if normal walking already hurts. The key is that you are not trying to win an argument with the pain. You are gathering cleaner information while avoiding the mistake that turns two bad days into six bad weeks.

Common scenarios

A useful example is the runner who finishes a mountainous long run on Saturday and can barely descend stairs on Sunday. Both quads are sore, the discomfort is dull, and after fifteen minutes of very easy jogging on Monday the legs feel less wooden. That usually supports an easy aerobic run or cross-training day, then a recheck before any quality work.

Compare that with the runner who finishes a normal midweek run and notices a very specific ache on the inside of the shin. It is tender in one spot, hurts with hopping, and becomes more noticeable the longer they run. That is a very different decision. Even if the pain level is not dramatic yet, the pattern is concerning enough to stop impact loading and monitor closely.

Or take the athlete whose calves are globally sore after their first real block of uphill treadmill work. If walking is fine, there is no focal tenderness, and the soreness is already fading by day three, training can usually continue with adjusted intensity. The best next step is often to keep running easy and postpone faster work until the calves are no longer changing your stride.

The mistake of making up missed training

One of the biggest errors after soreness is trying to preserve the original week at all costs. A runner skips Tuesday intensity because the legs are still beat up, then tries to cram the workout into Wednesday, keeps Thursday medium long, and arrives at the weekend carrying three days of unnecessary fatigue. The soreness itself was not the real problem. The poor adjustment was.

If you need to change the week, change it cleanly. Move the key session, shorten it, or replace it. Do not pretend the body is running on the original schedule when it is not. If that sounds familiar, how to adjust training after missing three days covers the same principle from a missed-training angle.

When soreness may reflect under-recovery, not just hard training

Sometimes the issue is not one brutal workout. It is that normal training suddenly creates outsized soreness because your recovery capacity is lower than usual. Poor sleep, high life stress, low energy intake, dehydration, hot weather, and a dense run of moderate-hard days can all shift how your body responds.

That is one reason soreness should never be judged in isolation. If your heart rate is unusually high for a normal easy pace, if you are seeing more drift than expected on steady runs, if motivation is low, and if soreness keeps lingering longer than normal, the right decision may be to reduce load for several days rather than treating each sore run as a separate mystery. A steady run that shows unusual heart rate drift can be one clue that the system as a whole is under more strain.

When to get medical help

Some situations move beyond self-management quickly. Seek medical assessment sooner if you cannot walk normally, if pain is severe, if there is significant swelling or bruising, if you suspect a muscle tear, or if bone pain is focal and impact-sensitive. Illness symptoms, chest symptoms, or calf pain with swelling also deserve proper medical attention rather than training experimentation.

For everything else, you do not need perfect certainty. You need a reasonable read of the pattern and a sensible next step.

If you wake up tomorrow with broad muscle soreness that matches the work you did, jog easily for ten to twenty minutes and see whether the legs settle. Keep the day aerobic. Recheck the following morning before deciding on intensity. If instead the pain is focal, sharp, or changes your gait, remove the workout from the day, switch to non-impact training or rest, and judge the next 48 hours by whether the symptoms clearly improve. That is how you protect the weeks that matter most.

Written by Wade Wegner. Train Ultra is a private AI coach that reads every workout you post to Strava. Try it free.