Time discontinuity detected

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
abs7125

Posts: 17
Joined: Mon Aug 27, 2018 3:40 pm
Location:

HTPC Specs: Show details

Time discontinuity detected

#1

Post by abs7125 » Fri Jan 25, 2019 12:04 am

Started getting this error today, on several channels, during update.
1/24/2019 4:50:58 PM] [ INFO] Time discontinuity detected. Service 10150 (COMEDYP) SH012857740000 (entry 755) ends at 2019-02-11 00:10:00Z, SH011281150000 (entry 756) starts at 2019-02-11 00:00:00Z.

abs7125

Posts: 17
Joined: Mon Aug 27, 2018 3:40 pm
Location:

HTPC Specs: Show details

#2

Post by abs7125 » Fri Jan 25, 2019 12:05 am

Forgot to add, I updated to latest version, cleared cache.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#3

Post by garyan2 » Fri Jan 25, 2019 3:19 am

The time discontinuities are from the data provided by Schedules Direct. This is usually due to Gracenote updating the data at the same time that Schedules Direct is downloading and caching it. It will usually clear up on the next run. If it persists, then you might want to notify SD ... though 2/11 is still a pretty good ways out to even be concerned about.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

abs7125

Posts: 17
Joined: Mon Aug 27, 2018 3:40 pm
Location:

HTPC Specs: Show details

#4

Post by abs7125 » Fri Jan 25, 2019 4:26 am

Ok, thanks for the reply. I will give it a day or so, if it doesn't change, I will let you know.

User avatar
StinkyImp

Posts: 669
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#5

Post by StinkyImp » Fri Jan 25, 2019 5:08 pm

It's been my experience that these "time discontinuities" will clear themselves and aren't anything to worry about. I've experienced these eight times over the past two years and dug into it in August 2018 when it seemed like I was getting them pretty frequently.

With no intervention on my part, they corrected themselves over the course of 12 days.

Code: Select all

EPG123 Log Parser (and Report Generator)
Report Created on 01/25/2019 at 09:51:50
================================================================
     1 [10/22/2017 2:00:26 AM] [WARNG] Time discontinuity detected. Service 95625 (KUTPDT4) SH012857740000 (entry 364) ends at 2017-10-30 15:30:00Z, SH001694340000 (entry 365) starts at 2017-10-30 04:30:00Z.
     2 [5/8/2018 12:15:21 AM] [WARNG] Time discontinuity detected. Service 35156 (KTVWDT) SH012857740000 (entry 82) ends at 2018-05-11 05:00:00Z, SH028543790000 (entry 83) starts at 2018-05-11 02:00:00Z.
     3 [6/20/2018 12:15:22 AM] [WARNG] Time discontinuity detected. Service 107788 (KDPHLD2) SH012857740000 (entry 249) ends at 2018-06-29 13:30:00Z, SH013903630000 (entry 250) starts at 2018-06-29 08:30:00Z.
     4 [8/11/2018 12:15:25 AM] [WARNG] Time discontinuity detected. Service 35176 (KFPHDT) SH012857740000 (entry 32) ends at 2018-08-12 03:00:00Z, MV000244330000 (entry 33) starts at 2018-08-12 01:00:00Z.
     5 [8/11/2018 12:15:28 AM] [WARNG] Time discontinuity detected. Service 109146 (KTVWDT6) SH012857740000 (entry 32) ends at 2018-08-12 03:00:00Z, MV000244330000 (entry 33) starts at 2018-08-12 01:00:00Z.
     6 [8/12/2018 12:15:26 AM] [WARNG] Time discontinuity detected. Service 35176 (KFPHDT) SH012857740000 (entry 1) ends at 2018-08-12 03:00:00Z, MV000244330000 (entry 2) starts at 2018-08-12 01:00:00Z.
     7 [8/12/2018 12:15:32 AM] [WARNG] Time discontinuity detected. Service 109146 (KTVWDT6) SH012857740000 (entry 1) ends at 2018-08-12 03:00:00Z, MV000244330000 (entry 2) starts at 2018-08-12 01:00:00Z.
     8 [8/23/2018 12:15:20 AM] [WARNG] Time discontinuity detected. Service 49104 (KTVWDT2) SH012857740000 (entry 1) ends at 2018-08-23 04:00:00Z, SH015992490000 (entry 2) starts at 2018-08-23 00:00:00Z.

===== QUERY INFORMATION (Predefined) ===========================
File Name:		OK_TO_DELETE_Merged Log
Search String:		Time discontinuity
Date Range:		02/05/2017 thru 01/25/2019
Total results found:	8
Query time:		36 seconds

===== GENERAL INFORMATION ======================================
Total lines processed:	54941
Logfile timespan:	2/5/2017 thru 1/25/2019

abs7125

Posts: 17
Joined: Mon Aug 27, 2018 3:40 pm
Location:

HTPC Specs: Show details

#6

Post by abs7125 » Sun Jan 27, 2019 9:22 pm

I sent schedules direct an email yesterday regarding this, and no errors today.

Post Reply