> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/live-tracking/refresh-event-data.md).

# 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.

{% hint style="info" %}
This is uncommon but can happen after a Racemap platform update. The good news: it is always fixable in seconds, without contacting support.
{% endhint %}

### 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:

1. Open your event in [Racemap](https://racemap.com)
2. Go to **Essentials → Basic**
3. Add one second to the end time (e.g. `14:00:00` → `14:00:01`)
4. Click **Save**
5. 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.

{% hint style="info" %}
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.
{% endhint %}

### 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.racemap.com/live-tracking/refresh-event-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.