What to Do When Your Long Run Falls Apart

A long run that falls apart matters because ultramarathon training depends on these sessions to build durability, pacing judgment, fueling skill, and confidence. When one goes badly, the temptation is to either panic and rewrite the whole block or shrug and pretend it meant nothing. Usually the right answer is in between. A failed long run is information. The useful question is not whether the run was bad. It is why it went bad, and what that means for the next few days.

Most long runs do not fall apart for mysterious reasons. They usually unravel because one of a short list of stressors got too large for the day: pacing was too ambitious, fueling came too late or too low, heat and dehydration raised the cost of the effort, accumulated fatigue reduced what you could absorb, terrain was harder than expected, or early signs of illness were already present. Sometimes more than one is true. A hot day plus modest dehydration plus an overexcited first hour can look like a complete collapse by hour three.

The first step is to define what “fell apart” actually means. For one runner it means pace slowed by 45 to 60 seconds per mile while effort climbed. For another it means planned easy effort turned into survival jogging, or the last hour became repeated walk breaks that were not part of the session. In trail running it may show up less as pace and more as loss of climbing power, trouble eating, rising heart rate at the same grade, poor coordination on descents, or a sudden sense that the run became much harder than the terrain justified.

What you felt during the run matters as much as the file afterward. If the first half felt smooth and the second half gradually became harder, fueling, hydration, pacing, and heat become more likely. If the run felt wrong from the start, accumulated fatigue, poor sleep, residual soreness, or illness move up the list. If your heart rate drifted upward while pace stayed steady, that points toward rising physiological strain rather than sudden fitness loss. If you have not read much about that pattern, cardiac drift in running is worth understanding, because it often explains why a reasonable long run can become unreasonably expensive late. If you want help sorting that pattern in your own training, the Train Ultra coach can help you think through what your workout data is actually saying.

A practical review starts with four observable signals.

Start with the signals you can actually trust

First, look at the shape of the run. Did it deteriorate gradually, or did it fall off a cliff? A gradual fade usually points to fueling, heat, hydration, or opening too fast. A sharp collapse can happen when carbohydrate availability gets too low, but it can also reflect GI trouble, a sudden spike in temperature exposure, or a mechanical problem like calf tightening or quad damage from descents.

Second, look at effort relative to output. If pace slowed a lot while heart rate stayed unusually low, deep fatigue, glycogen depletion, or muscular damage may be more relevant than cardiovascular strain. If heart rate was unusually high for an easy long run, heat, dehydration, illness, stress, or incomplete recovery are more likely. If both pace and heart rate dropped while you felt terrible, the issue may be more systemic than motivational.

Third, review fueling and fluid timing, not just totals. Sports nutrition research and practical race coaching agree on a point many runners miss: once you are clearly behind on carbohydrate intake, it is hard to fully recover within the same run. If you waited 70 to 90 minutes to start fueling, took in very little early, or skipped intake because the pace felt easy at first, that alone may explain the last third of the run. The same applies to fluid on hot days. By the time thirst, sloshing, or dizziness are obvious, the problem is no longer preventive.

Fourth, compare the run with the previous 7 to 14 days. Long runs rarely fail in isolation. A heavy work week, poor sleep, extra vert, travel, strength soreness, a hard workout two days earlier, or a string of “easy” runs that were not actually easy all change what your body can do on Sunday. If your easy pace has been trending slower or your normal effort has felt unusually costly, that broader context matters more than one ugly file. If that sounds familiar, why your easy pace suddenly got slower gives a good framework for reading that pattern.

The most common causes, and how they usually look

Pacing errors often hide in the first hour. The run feels controlled, heart rate looks fine, and the athlete tells themself they are just having a good day. On roads this might mean drifting from easy to steady. On trails it might mean pushing climbs a little too hard, running technical descents with too much braking, or treating the long run like a fitness test. The cost shows up later. Research on endurance performance consistently shows that early overpacing increases carbohydrate use, heat production, and perceived effort later in the session. If the run started a touch too hot and faded predictably, pacing is a leading suspect.

Underfueling is another common reason. For long runs beyond roughly two hours, especially when terrain or intensity is meaningful, carbohydrate intake during the run strongly affects how well you sustain output and coordination. As a starting point, aim for 60 to 75 grams of carbohydrate per hour on easy runs over two hours, and 75 to 90 grams per hour on long trail runs that mix easy and moderate running. Many ultrarunners know this in theory but still underfuel in training because the session is “only easy.” The problem is that easy by pace is not always easy by metabolic cost, especially on climbs, in heat, or when carrying fatigue. If you finished the run craving sugar, felt mentally foggy, got shaky, or had a dramatic drop in drive and leg power, low carbohydrate availability is high on the list.

Heat and dehydration increase the cost of any pace. As core temperature rises and plasma volume falls, heart rate tends to climb to maintain output. This is one reason hot-weather long runs can look like fitness loss when they are really a thermoregulation problem. Integrative work on late-race fatigue in marathon and ultra settings points to the combined effect of glycogen depletion, thermoregulatory strain, dehydration, and cardiovascular drift. In plain terms, fuel, fluid, and heat act together. A run can fall apart even if no single variable looks catastrophic.

Accumulated fatigue is the cause runners most often underappreciate. If your training load has been high, your sleep poor, or your life stress elevated, the body may simply not have enough reserve to turn a routine long run into useful adaptation. This does not mean the block has failed. It means the session happened on the wrong day for your current recovery state. The correct response is often to reduce load briefly, not to force another proving session.

Terrain-specific muscular damage also matters for ultrarunners. A long descent-heavy route can trash quads even when aerobic effort looks moderate. A steep hiking-focused run can expose local muscular endurance limits before your heart and lungs become the limiter. If your breathing was manageable but your legs lost force, especially on climbs or descents, this is not the same problem as classic bonking.

How to decide what the bad long run means

A single failed long run usually belongs in one of three buckets.

The first bucket is execution error on an otherwise normal training background. You started too hard, fueled poorly, underestimated the heat, or chose terrain that made the session harder than intended. If you were otherwise recovering normally before the run, this is the most likely explanation. The training implication is small. Learn from it, recover normally, and continue.

The second bucket is a run that exposed accumulated fatigue. In this case the long run did not fail because the plan was wrong, it failed because your body could not absorb it that day. Clues include several days of flat legs beforehand, rising effort on easy runs, unusually poor sleep, irritability, lower motivation, or lingering soreness. Here the implication is larger. The next few days should absorb fatigue, not dig deeper.

The third bucket is a warning sign for illness or injury. Stop-and-go worsening symptoms, chest symptoms, dizziness, unusual shortness of breath, one-sided pain that changes your stride, or soreness that localizes sharply rather than behaving like normal muscle fatigue deserve more caution. This is where bravado becomes expensive.

The decision rule is simple. If the cause was mostly execution, keep the week intact with minor changes. If the cause was mostly fatigue, reduce the next 48 to 72 hours. If the cause may be illness or injury, prioritize health over plan continuity.

What to do in the next 24 hours

Do not rush to make up the missed work. A long run that already took more than it should is not repaired by adding miles the next day.

Start by asking whether you can identify a clear, non-threatening explanation. If the answer is yes, for example you took in almost no carbs for two hours on a warm day and your heart rate drifted 12 beats while pace slipped, the next day should be easy or off, with emphasis on eating, drinking, and sleeping well. Resume training when your normal easy effort feels normal again.

If you cannot identify a clear explanation, or if your legs were dead before the run even started, make the next day a true recovery day and downgrade the next key session unless you feel clearly better. Most runners lose less from one conservative adjustment than from trying to force normal training through unresolved fatigue.

If symptoms suggest illness, especially fever, chest tightness, unusual breathlessness, or systemic fatigue out of proportion to the run, take a more medical view and less of a coaching view. Exercise physiology can explain a lot, but it should not explain away warning signs.

How to adjust the next few days

If the long run failed because of pacing, fueling, or heat, keep the adjustment modest. Take one easy day or rest day, then return to training with the next key session only if easy running feels normal. Do not stack punishment on top of the lesson. Instead, correct the process. Plan exact carbohydrate intake for the next long run, start earlier if it will be hot, slow the first hour, and match terrain to the purpose of the session.

If the long run failed because of accumulated fatigue, reduce load for 48 to 72 hours. That usually means replacing the next workout with easy running, shortening volume by 20 to 40 percent for a couple of days, or taking an extra rest day. Then reassess. If your legs and easy pace rebound, you likely caught the problem early. If not, keep the week flexible. The article on how to adjust training after missing three days is useful here because the principle is similar: protect the next seven to ten days more than the missed or failed session. A coach who is tracking the pattern across your week can also keep one bad day from turning into three, which is the point of an evaluation of every workout.

If the long run exposed muscular damage from terrain, do not judge recovery by aerobic freshness alone. You may feel eager to run while your quads or calves are still absorbing heavy eccentric stress. Easy flat running, hiking, or cross-training can be a better bridge than immediately repeating another hilly session.

A simple example

Suppose you planned a four-hour trail long run with steady aerobic effort. The weather ends up warmer than expected. You run the first 90 minutes by feel, take only one gel, and push the climbs because the group is moving well. By hour three your heart rate is 10 to 15 beats higher at the same effort, your downhill coordination is worse, and you start alternating running and walking on terrain you normally handle. You finish depleted and frustrated.

That run does not automatically mean your endurance is lacking. The most likely reading is execution plus environment. The next move is not another hard long run on Tuesday. It is a recovery day, solid carbohydrate intake that afternoon and evening, normal hydration, and an honest look at the first half of the run. Then, later in the week, you return to training and set clearer rules for the next long run: easier first hour, earlier fueling, and more respect for the heat.

Now change the example. Same fade, but this time your easy runs all week felt heavy, sleep was poor, work stress was high, and your resting mood was off. The long run probably revealed fatigue more than a fueling mistake. In that case you should cut back the next two or three days and remove intensity until your normal aerobic running returns.

The point is not to diagnose perfectly. It is to avoid the two most expensive mistakes, overreacting to one bad session, or ignoring the signal and repeating the same setup next weekend.

A long run that falls apart should make your next decision better. In the next few days, aim to restore normal easy running first. Then fix the most likely cause, one level deeper than the surface disappointment. If the problem was pace, slow the start. If it was fuel, eat earlier and more consistently. If it was heat, adjust expectations and logistics. If it was fatigue, make room for recovery before asking for another big aerobic cost.

Written by Wade Wegner. Train Ultra is a private AI coach that reads every workout from Garmin, COROS, Apple Health, or Health Connect. Try it free.