Keep guide and media updates distinct
A channel guide contains schedule information. A live media playlist describes currently available media for that stream. Refreshing the guide can update programme names without changing a stale media response. Identify which list you actually observed.
If diagnostics expose sequence advancement or response timestamps, record the field and time. A player spinner alone does not prove that the playlist was fetched or that an intermediary cache served it. Avoid assigning a cause before the request stage is known.
Use a current authorized session
Reopen the same current item through the normal supported flow once, noting whether it rejoins live playback. Record whether the player had been paused or disconnected. A client behind a moving live window has a different problem from a newly opened current session receiving unchanged publication data.
Do not append random query fields or edit private segment paths to force freshness. Signed or application-specific addresses can depend on their exact values. A changed URL is a different request, not a neutral refresh.
Compare evidence across one controlled interval
An illustrative source can return a successfully loaded playlist at two times while the listed current media does not advance. That observation is useful, but it does not identify whether the origin, cache policy or application state is responsible. The operator needs the actual resource and response context.
Compare one other permitted current item in the same player for scope. If it advances normally, retain that working example. A server permission error on the first item should be reported separately rather than treated as a stale-cache confirmation.
Escalate the narrow publication question
Provide time zone, item label, player version, fresh-versus-resumed state and any safe update evidence. Remove tokens and full media addresses from screenshots. Ask the operator to inspect the current publication and caching path associated with the incident.
After a correction, retest the original live item over a comparable interval. A one-time successful fetch does not establish continued advancement. The useful outcome is current playable media through the intended flow, with guide accuracy, reachability and freshness kept as separate observations.
Related questions
Should I erase all EPG data to repair a frozen media playlist?
Not without evidence. Schedule data and live media publication are different layers, and broad clearing can remove useful context.
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.
- MDN: Cache-Control header — Header semantics only; examples are illustrative.
