Activities Page not showing data

I mentioned it on here last week and get the same problem, strange so few seem to get it

Yeah, it's a strange one. At least it's not just me then.

Yeah, it's a strange one. At least it's not just me then.

but not many of us so will raise a fault with Garmin

it's always a problem

Lately if I do more than two activities and yes I do save it. When I connect to load up my activity stats..ONLY the last activity I did shows up..and all the stats from the first activity are gone?
Mind you, this is only recent. When I first got this I could do multiple activities save it and it would show up each one I did. Is this Vivohr not able to maintain more than one activity??

but not many of us so will raise a fault with Garmin

Raised the fault and asked for more details of course. Others must be having this problem

It will be interesting to see how widespread it is and if there is a fix.

I see the activities but can't open them, nothing happens when I click the link...

So surprised not many complained but this is the fix and applied correctly

First of all, please accept our apologies for not answering your email in the time we quoted on our website. Due to an unforeseeable high volume of emails and calls we’ve received this has led to a backlog, which we’ve been working hard to restore to our usual service levels.

From time to time a user may enter the Settings section of their Garmin Connect account to make adjustments. While there, users may change multiple fields including their Heart Rate Zones and Power Zones.

If a user adjusts the Watts of Zone 1 of their Power Zones to begin with the value of 0, the settings page will save this value and adjust all other zones accordingly. However, this will then create the NaN value.18 error on the Activities page of a user's account.

To resolve this error, the Watts of Zone 1 within the Power Zone setting needs to be a value greater than 0 (i.e. 100). Once this value is above 0, the NaN value.18 error will no longer appear.

Thanks Ianrobo. Only reading this now. Tried the fix and it's resolved. Didn't even realise I had Z1 set to 0!! Lesson learned anyway :p