Separate current playback from retained history
A programme guide can retain past schedule entries while a live media playlist advances. The guide and the media window serve different roles. A past title remaining visible does not establish that the corresponding video can still be requested.
Likewise, a pause button does not guarantee indefinite time shifting. The player, source and account's actual supported features determine what happens after a long pause. Obtain the real replay conditions for an essential programme rather than inferring them from the interface.
Consider the age of the reference
Record whether the player was newly opened, paused, disconnected or left idle before the failure. A stale live reference is different evidence from a fresh current playlist whose first segment fails immediately.
An illustrative window might move from segments 100–104 to 110–114 while a client remains paused. A later request for segment 102 may no longer be valid at that source. The numbers show sequence movement only; they are not timestamps, retention guarantees or this service's configuration.
Rejoin through the ordinary authorized flow
Use the player's supported return-to-live or reopen-current-item action where available. Do not guess earlier segment addresses or treat a missing old piece as permission to retrieve another account's archive. Record whether current playback works after rejoining.
If the fresh route still fails, keep the actual response and stage. A 404 for an old segment and a 403 on a new current request are different questions. The second should not be dismissed automatically as an old-window problem.
Report the narrow result
Provide the pause or disconnect context, time, item label, player version and whether rejoining current playback succeeded. Keep full playlists and media tokens private. If catch-up is the intended task, ask about a confirmed replay path rather than stretching a live-window model into an archive promise.
A successful return to live supports that current sample. It does not recover the missed portion automatically or guarantee a fixed period of pause tolerance. Keep the actual feature and account conditions beside the technical explanation.
Related questions
Does a live sliding window establish seven-day catch-up?
No. A current live window and a service replay archive are different features.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- RFC 8216: HTTP Live Streaming — HLS playlist and delivery mechanisms; examples are illustrative, not service measurements.
- Apple Developer: Live playlist sliding-window construction — Relevant HLS publication mechanism; illustrative household comparisons are editorial, not a service test.
