I have an odd issue involving the power curve data in connect. I use a service to sync my Peloton ride to Garmin. The ride data is usually EXACTLY 30min (or whatever the corresponding class length was on Peloton). The problem is that Garmin Connect doesn't recognize the full length.
Here's an example: Yesterday I completed a 30min ride wherein I set a personal record for average power over 30min...Yay. But, when the data was synced into connect, I didn't get any credit for the 30min power record. In other words, the power curve wasn't updated with my new 30min best.
I looked at the TCX file and confirmed that the time difference between the first and last track points was indeed, exactly, 30min.
To test my theory that the precise time was the issue, I added another trackpoint to the end of the TCX file for additional second. After uploading this file, voila, the power curves were updated.
To summarize: If I take two identical TCX files, but add an extra second to one of them, then upload them via connect web, the shorter one (exactly 30min) will fail to register a 30min power average. The longer one (30:01) WILL register a 30min power average. Essentially Garmin Connect is requiring >30min of power data in order to register a 30min power average.
So, how can I get Garmin Connect to actually record the 30min data when the activity is EXACTLY 30min long?