A wall-clock label can be ambiguous
A date, hour and minute usually identify a local moment well enough for everyday conversation. During a backward seasonal transition, however, the clock repeats part of the night. The same local label can then correspond to two UTC instants.
A system handling programme data should retain the UTC offset or equivalent disambiguation along with the local label. A viewer can make a reminder clearer by retaining the source’s full announcement instead of reducing it to 1.30 in a handwritten note.
Do not delete a listing just because the local hour repeats
Two guide entries with the same local label are not automatically duplicates. Compare their full timestamps, programme identities and source offsets. Conversely, a genuine duplicate can still exist; the repeated hour only explains why matching local clock text is insufficient evidence.
A live event, a repeat and a recording also remain different programme types. The time-zone rule does not decide which one a broadcaster intended. Use the programme’s description and timestamp together.
A reliable export retains an unambiguous timestamp
For a support example, keep the original timestamp or UTC instant and the time zone used to display it. A screenshot containing only the clock label can lose the information needed to reproduce the result. This is a data-interpretation issue, separate from video buffering or account activation.
Questions about this guide
Can a local time identify two different moments?
Yes, during a backward clock transition. The offset or UTC instant distinguishes the occurrences.
Does a repeated clock hour prove duplicate programmes?
No. Compare full timestamps and programme identities before treating entries as duplicates.