My 22-mile run ended at mile 8.
The other 4.87 miles were a limp back to my car.

Four weeks out from the Sugarloaf Marathon, that’s… not ideal.

Here’s the quick version:
My calf started grumbling around mile 5. By mile 6.5, it fully locked up. Hard, painful, not negotiable. I pushed to 8, stopped… and couldn’t start again. The muscle was a rock. Walking hurt. Running wasn’t happening. So I turned around and walked back. In shorts. In 40 degrees. Recording a video to keep from crying. Totally normal behavior.

And here’s where most runners spiral.

Because the immediate thought is:
Well, that’s it. Marathon’s over.

And it’s exactly what I thought during that long walk back to my car.

But it’s not.

Here’s the part most people get wrong:

One bad long run does not erase your fitness.
It doesn’t undo months of consistent training.
And it definitely doesn’t mean you suddenly “can’t” run your goal race.

What it does mean is that something—fatigue, compensation, load, mechanics—finally had enough so your body said, “we’re done here.”

That’s not failure. That’s information.

And this is where the shift needs to happen—especially late in a training cycle.

A bad long run isn’t a fitness problem to fix.
It’s a signal to interpret.

Because at 3–4 weeks out, your fitness is already built. You’re not going to suddenly gain endurance by cramming in another long run or doubling down on mileage. The only thing you can do at this point is protect what you’ve built—or chip away at it.

So instead of asking: How do I make up for this?
The better question is: What does this change about the next 7–10 days?

For most runners, the answer is some version of:

  • Back off just enough to let things settle

  • Keep easy runs actually easy

  • Be selective about what workouts you keep

  • And don’t force anything your body is clearly not ready for

Because the real risk isn’t the failed run.
The real risk is the overreaction to it.

This is how small issues turn into race-day problems—by trying to “win back” a workout that doesn’t matter anymore.

At this point in a marathon cycle, you’re not building fitness—you’re managing it.

You’re managing fatigue.
You’re managing niggles.
You’re managing how much stress your body can absorb without tipping over.

And sometimes that means doing less… not more.

So no, I’m not thrilled.
Yes, I’d much rather have finished that run exactly as planned. I had a bad week and was looking forward to the 22-miler building my confidence back up. Double-whammy.

However, after evaluating what had happened, and a couple of hours of improvement, I realized that the marathon is not off the table - nor is my goal of achieving a PR. It just means that my schedule is changing for the next week.

So a long run that flopped? It’s a part of training.

Not the highlight reel.
The part that actually matters.

I’ll recover, adjust, and get back to it. After weeks of training, I will happily take that view — this was just information, not a guarantee the race is off the table.

And yes—
the goal is still sub-four.

Keep on running!

~Jess

P.S. Want to watch the limping in action? Here’s my vlog on the debacle that was this week’s long run.

Reply

Avatar

or to participate

Keep reading