Workout load v target difference

These are my settings. In my understanding, that means training load should be based on pace. Workouts on my watch (Garmin) should use HR targets if they are there (and then use pace as a backup?)

Here is a workout.

If I set the radio button to ‘auto’ or HR then it has load of 16. When synced to the watch, this sets my alerts based on HR.

If I swap the radio button to pace then the load increases to 24. When synced to the watch, this sets my alerts based on pace.

Is this a bug? Do I just not understand how to use the feature properly?

In the planned workouts it follows the priority settings when on ‘Auto’. Else it follows what you select for Load.
In a finished activity it will always follow the priority setting.

That seems to have worked to calculate load.

However it doesn’t seem to have automatically associated the activity with the planned workout and if I drag it on there is that discrepancy which leads to it saying the compliance is that far off.

It won’t automatically pair of it’s outside these parameters:

The colours are as follows:

  • Between 80% and 120%: Green
  • Between 50% and 150%: Orange
  • Otherwise red
1 Like

Planned load = 16 (based on pace because of your priority setting)
Done load = 26 also based on your priority setting for activity load
26/16 = 1.63
So that’s all correct and auto pairing didn’t work because of the big difference.
Either change zones to better match for pace & HR, or set both with same priority.

That’s what’s confusing me.
My average HR of 121 bpm is firmily ‘in zone 1’ and the target of 60-70% is also zone 1.
My sub-T pace (based on a 20 min 5k) is 4:17/km. Based on that my zone 1 is 5:37/km or slower. That run has an average of 5:57 so 20s slower than my zone 1. That’s also possibly optimistic and a 5k now might be closer to 21:00 but that’d just make my pace be a higher load right?

To me those loads should be similar - not so widely different.