Strava Data-caching

Published by marco on

Strava makes for strange conversations: I’ve had discussions with nearly non-technical cycling colleagues about “eventual consistency” and caching and shared servers and data regions. It’s a funny old world.

In the two shots below, Strava is telling me that I got my second-best time[1] but the time for each activity is clearly lower than the time that it’s indicating as a PR. Even after recalculation, Strava is adamant. I’m not sure what could cause this as it’s pretty basic math. Maybe the numbers they’re showing are different than the numbers they’re using to calculate aggregated values (like PRs).

 Mauer Climb PR

 Maur Bergsprint PR

The next one is a bit of a twist: when I looked at a friend’s segment, I was wondering when I’d last ridden it, so I showed “My Results”. There I saw that Strava claims a different PR for that segment because it seems to have never updated it when I rode it faster earlier this year.

 Baumastrasse − Wirzwil

Strava sometimes caches too aggressively and it’s not immediately obvious how one gets Strava to recalculate.[2] Most likely you don’t; instead, you should just be happy that you were outside and stop sweating the numbers.


[1] For individual activities, you can refresh the achievements, but even after refreshing, my numbers were still incorrect.
[2] Which would have been fine, actually, as I wasn’t even trying to get the record.