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

Inaccurate Training Load

Hello,

I know there are countless of questions around this topic, but I believe this to be something new that started happening recently and I have not seen other posts about this specifically.

On Aug 17 I've done an exercise with load 418, as shown here:

However, the Training Load did not account for it, as if I didn't do that activity:



Then, the day after (8/18) it fixed itself but not retroactively (as in the value for 8/18 is correct, but not the 8/17 one):

I didn't do any activities on 8/18.

The same thing happened for several consecutive activities in the first week of August (you can see how it keeps going down despite me having trained most days and then it randomly jumps up on 8/9).

I've run the Training Load calculation myself in Excel to illustrate the issue:

It started this month, never had any issues before. It actually happened again today 8/23 so it's getting quite annoying now! It happens on all devices - phone, watch and web. Can you provide insights or fix the issue? Thanks

  • Can you provide insights or fix the issue?

    Not sure someone can do it, and Garmin rarely comments here on the user forum. I rather recommend reaching out to the Product Support through their website at https://support.garmin.com. Please post the resolution then here (if they offer one).

    BTW. which formula did you use for calculating the Acute Load?

  • Thank you for your reply, I will try the support link.

    The formula is a weighted average of the exercise load of the last 10 days multiplied by 7. So:

    (EL0*10+EL1*9+EL2*8...+EL9*1)/55*7

    Where EL0 is the sum of all exercise loads of the current day, EL1 of the day before, EL2 of two days before and so on.

    Cheers

  • I had same issue, I asked to the support but I never received a reply.

    BTW I had the issue only once, in a day of garmin server down, after that I no loger had the problem for the moment

  • Update - it's getting even worse, this is how it is differing now:


    Not only it does not account for some activities sometimes (like the big one I did on 9/1), but it's just generally inaccurate now.