Separate publication from the viewing product
A service can present a live event, a later on-demand edition or a replay feature through different resources. The same event title does not guarantee the same playlist, edit or availability window. Keep the exact selected listing with any diagnostic observation.
A player menu labelled catch-up does not prove that the source uses an EVENT playlist. Conversely, an event-style playlist can exist without a contractual promise that every earlier segment remains available forever. Resource publication and account conditions are separate layers.
Understand the growth distinction
An illustrative EVENT playlist might list the opening media and append more as the event proceeds. A fixed VOD playlist describes the completed media sequence without later additions under that type. The labels answer how the list changes, not whether the programme is free or downloadable.
A live sliding-window playlist is another pattern and should not be treated as an append-only event history. Old entries leaving a current live window do not by themselves establish an EVENT violation; identify the actual type first.
Diagnose the requested mode
Record whether the viewer tried current live playback, a marked replay or an on-demand entry. Note whether the failure occurs at opening, at a seek point or near the current end. Those actions can request different resources even when the title is similar.
Use the ordinary authorized list rather than an old saved deep link. If a current completed edition works while the old event link fails, retain that distinction. Do not guess segment addresses or edit a playlist type to manufacture an archive.
Ask the operator the relevant question
For technical publication, provide safe resource context, time and actual marker information where available. For viewing availability, ask about the exact programme, edition and account conditions. A protocol type cannot answer a commercial retention question.
After a supported correction, retest the original requested mode. A working later VOD edition may be a useful alternative, but it does not prove the earlier live path or replay function is restored. Keep the actual successful option labelled rather than declaring every mode fixed.
Related questions
Does EVENT mean every past event segment can be watched indefinitely?
No. Technical playlist behaviour does not establish permanent service availability, storage or permission.
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: Event playlist construction — Relevant HLS publication mechanism; illustrative household comparisons are editorial, not a service test.
