You are reading a single comment by @Greenbank and its replies.
Click here to read the full conversation.
-
Sure, it was just meant as an example of how their current architecture is probably responsible for huge numbers of these kinds of problems.
They tend to kick off an email the second something happens (e.g. your KOM was taken by person X) rather than holding off for a short while in case of any further changes (or fixing some obviously duff data, etc) but by the time you got to look at it person Y had uploaded their ride and taken the KOM from X.
I remember taking a KOM off someone when I uploaded a whole load of my old Audax GPX tracklogs. They would have looked at it and seen that their 2018 KOM was suddenly replaced by someone with a ride that took place in 2009.
Greenbank
I get what you are saying but doesn’t really explain my scenarios chain of events...