A reader may keep a local catalogue cache so the channel list opens quickly. A corrected remote source can therefore coexist with old names or entries on one device until its playlist refresh completes. Refresh the catalogue separately from the programme guide where the player treats them as different resources.
Identify which data is stale
An old channel name, a missing new group and an outdated programme title are not the same cache. Channel catalogue data and EPG data often have separate update actions. Choose the action that corresponds to the stale information.
Use a controlled refresh
Note the current entry and update status, then refresh once and wait for completion. Repeatedly interrupting the process can make it harder to know which version is loaded. Avoid clearing all application data for a single stale label.
Keep source and device evidence separate
If another authorized device shows the correction, that suggests a local update issue, though it does not prove the precise cache behavior. Record which device and profile were refreshed instead of assuming every profile shares one cache.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A renamed station can appear under its old label on one device while another has already refreshed the catalogue. Refreshing only the EPG may leave the channel name unchanged.
Questions about this topic
Does EPG refresh always update channels?
No. Readers can manage those datasets separately.
Should I erase the account to update one label?
Use the narrower refresh option first where available.
