A guide discrepancy around a clock change can come from the device’s time-zone rules, the source timestamps or an old manual adjustment. The date matters. A schedule that matched last week can be wrong this week even though no channel name or account field changed.
Avoid treating “one hour” as a complete diagnosis. A one-hour difference is a useful observation, but it does not identify which layer applied the wrong rule. Compare a dated programme across the transition before changing the whole guide.
Check the region and the date
Countries and regions do not all change clocks, and those that do may use different dates. A fixed UTC offset copied from a summer note is not a substitute for current named-zone rules. A regional legal change can also make an old seasonal assumption obsolete.
For guide data, inspect whether the programme timestamps carry explicit offsets. A source that supplies dated absolute times and a player that converts them locally have a different arrangement from a source interpreted through an added manual shift. Know which arrangement you are troubleshooting.
Compare a transition window
If the device clock itself is wrong, a guide-only shift can conceal the visible symptom while leaving other time-dependent features inconsistent. If the device is correct but one channel’s source uses the wrong time, changing the device zone spreads the problem beyond that channel.
- Choose one known programme before and one after the relevant date.
- Confirm the device’s intended named time zone and current clock.
- Inspect the source timestamps and their offsets where available.
- Record any manual global or per-channel corrections.
- Change only the verified faulty layer and compare both dates again.
Revisit old workarounds
A manual adjustment created months earlier can become the source of a new error. Once upstream data or device rules are corrected, the workaround may apply an extra shift. Keep a private note of its original purpose so it can be removed deliberately rather than adjusted repeatedly.
A guide can also cross midnight after conversion. Check the local date as well as the hour. An event that looks missing on one day may be correctly placed just after midnight on the next, especially when viewers compare a foreign announcement with their own local grid.
For support, supply the exact region, event date, expected time, displayed time and existing correction settings. Avoid “daylight saving is broken everywhere” when the evidence concerns one source or channel. A precise dated comparison can identify whether the fault follows the time-zone rule, the guide data or a remembered manual correction.
Useful answers
Does every country change clocks twice a year?
No. Verify the relevant region’s current rules.
Can an old manual guide shift become wrong after a source fix?
Yes. It can apply an additional correction after the original fault is resolved.
Why should I check the date as well as the hour?
Time-zone conversion can move a programme across midnight into another local day.