Bug report: Zwift activities + 7 day acute load

I've confirmed this looks like a backend issue (as I suspected).

The web client also shows the incorrect number (the Acute Training Load graph doesn't include the value from the Exercise Load graph for the latest day).

More than 12 hours after the activity, and the graph is still incorrect. Maybe it will fix itself when the day rolls over?

Hi, according to the Garmin website: "Acute load is formulaically a weighted sum of all training from the past week. It is not possible to arrive at the value simply by adding the load measurement in your recent activities." (Reference: https://support.garmin.com/en-CA/?faq=C6iHdy0SS05RkoSVbFz066). Maybe that's what's happening here. Cheers

Thanks, I take your point but the before value of 460 *didn't change* following the activity. As I had a hard but short 30 minute session (deliberately) I would have expected that figure to change.

There's definitely a bug somewhere there, and it's interesting if you add the load of the activities up ignoring the latest one, it comes to 460.

I managed to fix the problem by deleting the activity in Garmin Connect, downloading the.fit file from Zwift, and uploading it again manually.

Now 562, as expected. Clearly this was caused by a bug or glitch in the Garmin backend.

Hmm, you might be on to something there. Mine definitely don't add up exactly, although they are roughly close. I looked into this briefly recently and that's when I recall seeing the mention of "weighted sum" for the first time. (Also I don't recall it being called "Acute Training Load" in the past, only "7-day Training Load", that's something that seems to have arrived in recent Garmin Connect updates and newer devices. But maybe I just didn't notice it before.)

In any case I often don't check it immediately after upload, so if there is a delay, I just might not be seeing it. Also I don't sync Zwift directly to Garmin Connect, I "dual-record" using my Edge 530 and only upload that to GC. Sending Zwift rides direct to GC and having it update Training Status etc is still somewhat evolving. Around March 2023 it was modified from on-device processing (required a dual sync with a Garmin device to update in GC) to on-server processing (device sync not required), so maybe that new server processing has a lag for the ATL chart.

Virtual rides like Zwift do have dual timestamp tags in them, one for the virtual world location and one for my local timezone. I wonder if that ATL processing algorithm might be grabbing the virtual one, which would place the ride in the future and maybe delay it appearing in the ATL graph? Wild random speculation on my part though.

Anyhow I honestly have no answers, just spitballing ideas. If you do contact Garmin Support for an answer, please share the response here. Cheers

In zwift I've turned on Garmin uploads. That's how the initial activity in Garmin was uploaded. I waited more than 12 hours for processing.

I got fed up waiting (I figured it probably wasn't going to happen) so I deleted the activity in Garmin, manually downloaded the FIT file from Zwift and then uploaded that manually via the web console.

The training load was processed immediately and the graph was updated.

I might reach out to Garmin support and point them here as I feel this is a bug of some kind.

I pretty much did the same thing today (zwift activity, automatically uploaded). This time the graph _was_ updated, so it's intermittent.

I've passed it on to Garmin support. The ticket has been closed but I think there's a bug report now.

This may be unrelated but the latest Zwift release v1.48 includes some bug fixes for uploads to Garmin Connect: https://zwiftinsider.com/update-1-48-0-120544/

It sounds like it's for a different issue, but it may have affected this somehow.

That does look related. Hopefully the issue is been fixed as a result.

Another activity this morning went through and was processed unhindered.

So 1 bad activity, 2 good activities