FTP Stopped Being Updated

I recently had a 4 week or so break where I did no exercise. Before and after that, I have mostly been doing indoor and outdoor cycling with a bit of running occasionally. I have a power meter on my bike so both outdoor and indoor rides have power data and I always use a chest strap for accurate heart rate data. 

Now before the break Garmin was regularly updating my FTP, and it was usually very close to my ftp being tracked in a different platform that uses a different algorithm, which increased my confidence. Since the break though, the FTP chart just shows "No data available" even though I have been doing bike rides with power and heart rate data. Also it shows my VO2MAX went down a bit but I'm not even sure if for the last few rides it is even recording a VO2MAX. My vo2max is not budging though I feel my cycling performance is improving. 

I would appreciate if someone knowledgeable can tell me what is wrong. Should I open a service call with Garmin?

Thanks. 

----

Saad

  • I had the same issue , I had no update for ages, then it disappeared from Garmin Connect mobile, I was training regularly,  it should of moved, I then put in a lower ftp on the watch, and connect, so that next time out it has to see a better ftp, went for a few harder rides, again nothing, should of moved, factory re-set watch, and uninstalled connect mobile, no change, but this time the ftp data screen on watch gone as well, could not get it back, raised the point with Garmin uk, I was also having gps problems, got an exchange watch all good now, no problems except excessive battery drain.

     Try lowering your ftp on watch and connect to see if you can trigger it, if not factory re set watch and uninstall re install connect mobile, make sure your ftp is lower than you think it should be then try again, make sure your ftp is the same on watch and connect. The only thing that I changed for my ftp to stop updating was around that time I changed power meters from a stages single side, to Assioma duos, think that was just a coincidence though.