My ride from today also has a very close value, so Strava has backed their changes out
@eddiegrinwald thanks for following up with the team on this to see if a more robust integration would help avoid this dependency on Strava logic moving forward
1 Like
I asked for more info from Strava support, & Jimi (also a TR user!) provided
We believe the issue came from an update to our tcx file parsing. We rolled out a fix yesterday for missing/inaccurate Calories on TCX files so we are pulling calories from the file again. The fix only resolves the issue for activities going forward so any activities from the last week that had missing/inaccurate calorie data will need to be fully deleted and reuploaded.
I infer that the difference noted in this thread between TR & other uploading platforms (Garmin, &c) is the file format they use (presumably FIT?).
1 Like
Interesting!
We send over .TCX files as well. 
Sorry, yeah, that’s what I meant: TR sends .tcx, so was affected by the bug, but I was guessing that Garmin sent .fit so was not…