Past programme entries are schedule history. Catch-up television requires a separate replay source, service entitlement and player support. A guide can show yesterday’s title even when no recording or replay exists. Treat the ability to browse old listings and the ability to watch them as distinct features.
Look for an actual replay action
A reader may display a replay icon or a catch-up command only for supported entries. The presence of an old title alone is not that command. Follow the service’s instructions rather than constructing undocumented replay URLs.
Keep retention windows separate
The guide can retain more or fewer days than the replay service. A programme may remain in the grid after its replay window ends, or the guide may lack a title for a replay that exists. These are separate data-retention decisions.
Avoid promising recordings to other people
Reseller or household instructions should state only the replay features actually supplied. An EPG screenshot is not evidence of a guaranteed catch-up library. Ask about the exact supported window and restrictions before relying on it.
A practical sequence
- Check for a documented replay feature and entitlement.
- Compare the guide-history window with the replay window.
- Use only supported replay actions in the player.
An example
A seven-day guide history can coexist with no catch-up service. It can also coexist with a shorter replay window, depending on the actual service configuration.
Questions about this topic
Can I enable catch-up by keeping more EPG days?
No. Retention settings do not create a replay source.
Does every past listing have a playable archive?
No. Availability depends on the actual replay service and rights.
