Runs missing load, power

Some of these runs don’t have load. The ones that do, the power is straight across or stepped:


Even when there is load, my 10km runs should be roughly the same load, but I see 35, 37, then 145. A 12km run is shown as 40 load!

My run activity in my Garmin watch has power enabled and I see power in Garmin for these runs:

I really like the fitness graph, but now it’s showing my fatigue has fallen recently when I know that’s not true. Yesterday I ran 10km and the fatigue only went down. It shows me as almost fresh, but I hurt a lot! :smiley:

Any ideas why this happens? I’d love to be able to trust the fitness graph, but now I wonder how many previous activities aren’t affecting it.

There’s a chance the power stream is not being used correctly.

I forgot where to check but there’s a field called power / power2.

Try going to action menu and Fix Data perhaps.

Tried fix data, with all checked, says no data points were changed. Tried reprocess file, same result. Tried settings > ignore power data, then I got load 59 instead of ?. I guess that’s something, but I hope I don’t need to do that for every run.

The horizontal red line across your power indicates that it’s being clipped; you should see a message above your graphs saying “Power spikes of XX% or more above FTP based power curve have been fixed.” This means that your FTP likely isn’t set properly, if your whole exercise looks like this.

You can see the full data by adding the “Raw Power” chart, to confirm that this is the issue.

To fix, you’ll need to set your running FTP in your settings correctly. You can also loosen the restrictions by clicking that message, and changing the value for the power spike correction to something large, like 999%; if you do this, it should give you a new estimated FTP value that you can plug into the settings, if you don’t have a value from other source (like your watch).

Edit: To go back and fix your historical data, you can recognize which activities have been clipped in this way by the red circular icon with the lightning bolt visible on the activities in your screenshot.

2 Likes

Lasr screenshot shows a run FTP set around 270. Garmin data shows that you´re mostly over 5W/kg.
Chances are that your FTP is set too low. Post just above perfectly explains what to do.

1 Like

Some extra info:

By ignoring Power, Intervals will use the next priority for load calculation. Depending on your settings, that can be Pace or HR.

If you have Stryd or other second power on your watch next to wrist power, make sure to select which Power stream you want Intervals to use as default. Actions Settings:

2 Likes

Awesome, thanks for the help and info!

With 999% power spike correction I see:

Funny it says “ride” but cool it gives me a number. This is my first time encountering FTP but I’m happy to learn and I’ve now read up a little bit.

The 30% power spike clipping makes sense, though it’s hard to see in my power data if qualifying spikes are invalid and warrant clipping. If FTP is based on sustained power for 1 hour, I’m doing sprint intervals couldn’t I easily exceed 30%?

My settings were 212 FTP (at first I edited the wrong values, as Ride is default but I only run!) so I changed it to 330 with 30% threshold. Existing activities are still clipped. Is there a way to fix up ALL activities? I’d like the see my fitness for the past years, so fixing them up one-by-one is too tedious. I tried reprocessing a single activity (with nothing checked to keep), but the power was still clipped. Maybe I can delete everything, or possibly my account, and reimport, or just reimport without deleting first?

The spike protection coupled with needing to set FTP appropriately seems like a bit of a gotcha to new users. If activities are synced when FTP isn’t set correctly, all the loads are wrecked. Hopefully there is a way to fix it up easily.

I only have the one power data source.

FTP is more commonly known as a cycling value; running power is relatively new in comparison, so it’s not as widely recognized by runners. Garmin estimates it as “lactate threshold power,” available here in Garmin Connect: https://connect.garmin.com/modern/report/-39/running/current

You can edit FTP on past activities in bulk from the activities list view. On the activities page, select this middle icon to switch to list view:
image
Make sure the time range in the upper left is enough to contain all of the activities you want to change. You can use the dropdown that says “All activities” by default to further filter your activities if you need to (choose “Add” to add a field to filter by, then you can choose options for that field).

Check the boxes to the left of each activity you would like to edit (or the checkbox at the top of that column to select all visible activities), and select “Edit” from the “EDIT” dropdown menu on the top bar. In the window that comes up, you can enter a new FTP, and it will apply that to all selected activities when you hit OK.

As for your question about your sprint intervals, your FTP defines a curve based on a mathematical calculation, which is plotted as power vs duration. For shorter time durations, this curve will result in much higher expected power values compared to your FTP number. You can see a depiction of this curve in the window that appears when you’re changing your spike detection value, and if you mouse over that graph you can see the maximum values your spike detection will think is “real” for a given duration.

Edit: I will note that changing all of your past activities to your current FTP is going to result in a bit of invalid historical data; FTP changes over time (hopefully increasing as you get more fit), so comparing old activities to your current FTP may not give you exactly accurate Load values, but it’ll probably be close enough for now. As long as you keep your FTP value updated as it changes moving forward, you should be fine.

1 Like

Got it, much thanks! I believe I’m good to go now.

Having to keep FTP updated is not so convenient. Since I will just input the value from the data, couldn’t it be automated?

This is how I’m looking now:

There is an automated value that intervals generates called eFTP (estimated FTP); you can see this value from your Power page. Intervals will also alert you on an activity when your eFTP goes above your FTP (like it did when you changed your spike correction earlier) to alert you that you may want to change your FTP in your settings.

The values are different because you may want to use your results from a specific FTP test (common for cyclists) as the basis for your calculations, regardless of what intervals thinks your FTP is.

1 Like

If you have power spikes, they will be rather clear visually. Set Spike detection higher, something like 60-80% should do fine if you have no spikes. If you do see spikes, fine-tune the setting.

1 Like

Got it, cheers!

I set all my runs to 377 FTP and everything seems OK. I thought maybe they get set something when imported from Garmin, so I deleted them all and reimported (all, using the full Garmin export). They all came back, but still have 377 FTP. Do all imported activities get the FTP from my settings? That makes sense for new activities, assuming I keep it up to date, but maybe when importing it should use eFTP, or have an option for that. WDYT?

A new entry for FTP on an activity in the past, will be used for all consecutive activities thereafter, untill you enter another FTP. That´s how FTP history is used.
On the Activity List view, you can visualize the FTP column to check out the FTP used for that activity. And you can manually edit it there to if you want. That’s ok for a single activity but for bulk, better use the procedure explained above.

1 Like