Ask Tempo

Should I stop a run that's going wrong?

Tempo · 4 min read

Short answer: there's no single rule, because "going wrong" isn't one situation. A session that's simply gotten hard (heavy legs, ragged breathing, a drifting pace) is still doing its job. A sharp, specific pain that worsens as the effort continues is a different signal, and it calls for a different answer. Telling them apart is about what's actually changing, not about toughness.

What counts as "going wrong"

Running culture has a default answer for a session that turns ugly: finish it anyway. Stopping reads as weakness, cutting a workout short reads as quitting, and "push through it" gets repeated often enough that it stops sounding like advice and starts sounding like a rule. That instinct isn't wrong about everything: plenty of sessions are supposed to be uncomfortable. But it treats every kind of discomfort as the same discomfort, and it isn't.

Pace drifting off target, breathing that feels disproportionate to the speed, legs that went from tired to leaden somewhere past the midpoint: all of that is unpleasant, and none of it is automatically a reason to stop. Nausea, dizziness, a sudden pull in one specific spot, or pain that changes how a runner is moving belong to a different category entirely. The finish-it-anyway reflex doesn't distinguish between them, which is exactly where it breaks down.

The physiology underneath the split

Fatigue by itself isn't a warning sign. It's the expected cost of real work, and a demanding session is supposed to leave the legs depleted. What's worth watching is what changes underneath that fatigue. As muscles tire, running mechanics shift: stride length shortens, time spent in contact with the ground stretches, and the body starts compensating in ways that load tissue differently than when it was fresh. That shift shows up in what a run leaves behind, not only in how the session feels, and it's a large part of why the back half of a hard effort feels disproportionately harder than the front.

Pain that stays confined to one spot, stays sharp rather than dull, and gets worse rather than settling once the body is warmed into the effort is a different signal than general fatigue. Diffuse, symmetric discomfort that tracks with effort and plateaus is closer to ordinary training stress than tissue damage. Pushing through the first kind tends to turn one rough session into a much longer stretch of forced rest; pushing through the second kind is often just finishing what was already planned.

When finishing earns its keep

Some sessions are built to be uncomfortable on purpose, and different sessions are uncomfortable for different reasons. A threshold effort holds a pace just below what the body can clear efficiently, training it to buffer and clear that load faster over time; backing off at the first hard patch trims the exact stimulus the session was built to deliver. Race-pace work has a separate job: rehearsing the precise effort a race will demand, so the legs and the mind already recognize that speed when it counts. Finishing either kind of session, when the discomfort is effort rather than tissue, builds the specific tolerance that session was training.

None of that applies to an easy day that's supposed to feel easy. If an aerobic run suddenly turns into a grind for no clear reason, there's little sitting at the end of gutting it out, because the session was never built to produce anything from that. What a run was for changes the calculus far more than how tough it feels to finish it.

Deciding without a script

A few questions separate a considered stop from a reflexive one: is the feeling getting worse or holding steady, is it confined to one spot or spread across the whole effort, and what was this particular session actually built to do. A hard effort hurting is not new information. A sharp, worsening, localized signal on an easy day is.

Cutting a session short changes what the rest of the week can reasonably carry, whichever way the call goes. A fixed training plan doesn't know that happened. It just marches on to the next line as written. Telling Tempo what actually happened mid-run lets the remaining sessions get reconsidered against the underlying race goal, with the reasoning for any change laid out rather than buried, and room to disagree with it before anything changes.