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?) [CleanShot 2026-04-01 at 11.10.23@2x] Here is a workout. [CleanShot 2026-04-01 at 11.10.11@2x] If…

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.

[image] MedTechCD: In the planned workouts it follows the priority settings when on ‘Auto’. Else it follows what you select for Load. That seems to have worked to calculate load. [CleanShot 2026-04-01 at 18.19.47@2x] However it doesn’t seem to have automatically associated the activity wit…

[image] Dobow: However it doesn’t seem to have automatically associated the activity with the planned workout 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 [im…

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 wi…

[CleanShot 2026-04-02 at 09.42.25@2x] 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 …

Workout load v target difference

Bug Reports

Gerald 1 April 2026 18:28 4

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