This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

TE does not match Scoring Scale

In the run overview, Connect mentions an aerobic TE of 4.2. Also when I click the question mark symbol, it shows this number (see Fig. 1 below). It mentions this is a 'Minor Aerobic Benefit'. However, when I go to the Scoring scale tab, a TE of 4.2 should correspond to 'Highly Improving', see Fig. 2. A 'Minor Benefit' corresponds to a TE of 1 according to that table. So the description in the 'This Activity' and 'Scoring Scale' tabs do not seem to match. Do you see this problem as well?

Fig. 1



Fig. 2

  • No, I don't see it.

    From my last several runs recorded on two different Forerunner watches:

  • Thanks for testing. Strange. I tried on Chrome, Firefox and Edge, and all three show the same issue. I tried another activity of TE 5.0. Also there it shows the wrong description. Any ideas what could be the issue here? They were imported from a Forerunner 235.

  • very odd

    Must be a conversion(mi->km?)/language issue possibly.... notice you have a coma as the decimal... ?

    Unfortunately the TE score doesn't make much sense to begin with.... as it is listed as a 'aerobic training effect' yet a fast Tempo run or some intervals will have a higher effect than a 2.5hr run at 75-80% max HR...

    I like that they are improving on the TE, including it in the reports....etc. Really wish they would implement more of a smart training effect or training load/fatigue. Similar to the Strava 'Suffer score' or TrainingPeaks TSS - something that takes into account the level of exertion...and Duration.
  • Thanks! The comma/dot thing triggered me. I tried changing the notation in the settings, see the figure below. When I set the decimal character to a comma, I get the issue. When I change it to the dot character, everything shows fine again. So appears to be a bug in the Garmin website software.

    When I use the setting in the red box it goes wrong:


    When changing the decimal character to a 'dot':

  • So appears to be a bug in the Garmin website software.
    Yep, I'm seeing the same symptom of a software defect when I change the decimal separator from a period to a comma.
  • Former Member
    0 Former Member over 8 years ago
    Thank you for this discussion. This issue has been reported and we are investigating in order to resolve this issue.
  • Former Member
    0 Former Member over 8 years ago
    An update to Garmin Connect was pushed out yesterday afternoon and this issue has been resolved.

    Closing this thread. If you are still seeing this issue please start a new thread.