A player can retain programme-guide data locally to avoid rebuilding it on every view. That cache can be useful, but an outdated display may persist after the source has changed. Diagnose the difference between source freshness and displayed freshness before deleting all player data.
A refresh control and a cache control may affect different layers. One can retrieve a file while another rebuilds the application’s schedule database. Read the actual player documentation rather than assuming one button clears every retained copy.
Pick a concrete correction to track
Choose a dated change that should be visible, such as a corrected programme title or revised start time. A vague feeling that the grid looks old is difficult to test. Compare the source record and the displayed record for the same channel and event.
If the source itself remains old, clearing the local cache cannot create new listings. If the source contains the correction but the player still shows the previous value, retained local data or a different active source becomes a more relevant explanation.
Compare before clearing
Keep favourites, profiles and private account settings out of a broad reset unless the documented operation requires it. A guide-specific rebuild can have a much narrower effect than clearing the entire application. Understand the scope before confirming a destructive control.
- Record the current event label, time and channel on screen.
- Confirm the intended active guide source and its latest retrieval result.
- Inspect whether the current source contains the expected correction.
- Use the documented guide refresh or rebuild option appropriate to that layer.
- Reopen the same event window and compare the actual result.
Check for multiple retained copies
A downloaded local file can remain stale even if the player repeatedly rereads it. A remote-source cache can retain another copy. These layers should be named clearly in the maintenance note: the original remote data, the saved local file and the displayed guide database are not necessarily the same object.
Also confirm that a different profile or duplicate catalogue is not active. Two locally named sources can make the correct update appear absent when the viewer is looking at the older copy. Resolve identification before repeating the refresh.
A good support report includes the exact corrected source event, the older displayed value and the documented refresh used. That demonstrates a specific mismatch without claiming that all caching is broken. Once the display agrees with the current source, the result establishes this guide refresh in this setup; it does not verify future source accuracy or playback entitlement.
Useful answers
Will clearing a cache fix an old upstream guide?
No. The source must provide updated events.
Is a guide rebuild identical to clearing all app data?
Not necessarily. Check the operation’s documented scope.
Can a local file be reread successfully while remaining stale?
Yes. Repeatedly loading an unchanged snapshot does not obtain new source data.