Refreshing event data
Racemap pre-calculates and caches a lot of event data — participant positions, rankings, split times — so that maps and APIs can serve thousands of viewers at once without delay.
In rare cases, after a platform update that changes how data is calculated (for example, which participants appear on the map, or how rankings are sorted), your event's cached data may not refresh automatically. This can make it look like something is broken — participants missing from the map, wrong order on the leaderboard, unexpected API responses — even though your event settings are perfectly correct.
This is uncommon but can happen after a Racemap platform update. The good news: it is always fixable in seconds, without contacting support.
How to tell if this is the issue
Look at the "saved X ago" timestamp displayed below the event name in the top-left corner of the event editor. If the timestamp is many hours or days old and something in your map or leaderboard looks off, a stale cache is a likely cause — especially if the issue appeared after a recent Racemap update.
The fix: trigger a re-save
Any change to your event settings causes Racemap to fully recalculate and refresh the cached data. The safest approach is a tiny, reversible change to the end time:
Open your event in Racemap
Go to Essentials → Basic
Add one second to the end time (e.g.
14:00:00→14:00:01)Click Save
Reload your tracking map or leaderboard
The data should now reflect the latest platform logic. You can then set the end time back to its original value if needed — that save will also keep the data fresh.
If the issue persists after a re-save, please contact support. Include your event ID (visible in the browser URL) and describe what you expected to see versus what you are seeing — that helps us pinpoint the cause quickly.
Synonyms and search terms
This page covers problems also described as: stale event data, outdated cache, participants not showing, missing athletes, leaderboard not updating, wrong ranking, map not showing all runners, old data in API, event not recalculated after update.
Last updated