Only part of the guide was analysed
The guide is larger than the per-run limit, so the figures cover only the programmes we read.
What it means
Analysis stopped at the programme limit for a single run. Everything reported is accurate for the portion read, but counts and coverage are not totals.
Why it matters
Very large guides — hundreds of thousands of programmes across months — would take unbounded time and memory to process in one request. The cap keeps the tool responsive; it does mean gaps and coverage beyond the cut-off were not examined.
How to fix it
- Split the guide by date range or by channel group and check each part.
- If the guide covers far more days than your clients use, generating a shorter window makes it faster for everyone.
- Most clients only read a few days ahead, so a very long guide is often wasted bandwidth.
Check your own stream
The free EPG checker runs this check on every analysis and links each finding straight back here.
Open the EPG checker →Frequently asked questions
- What does "Only part of the guide was analysed" mean?
- Analysis stopped at the programme limit for a single run. Everything reported is accurate for the portion read, but counts and coverage are not totals.
- Why does it matter?
- Very large guides — hundreds of thousands of programmes across months — would take unbounded time and memory to process in one request. The cap keeps the tool responsive; it does mean gaps and coverage beyond the cut-off were not examined.
- How do I fix it?
- 1. Split the guide by date range or by channel group and check each part. 2. If the guide covers far more days than your clients use, generating a shorter window makes it faster for everyone. 3. Most clients only read a few days ahead, so a very long guide is often wasted bandwidth.
- How can I detect this automatically?
- Paste your XMLTV programme guides URL into StreamTest's free EPG checker. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.
Related Programme guides checks
- XMLTV timestamps have no UTC offsetTimestamps without an explicit offset are ambiguous, and are the usual cause of a guide that appears shifted by whole hours.
- XMLTV guide has holes in a channel scheduleConsecutive programmes do not join up, leaving blank stretches in the guide.
- XMLTV guide does not extend far enough aheadThe guide runs out within hours, so viewers lose programme information partway through the day.
- The guide is not well-formed XMLThe document could not be parsed as XML, so nothing else could be checked.
- The document has no <tv> root elementThe XML parsed, but its root is not <tv>, so it is not an XMLTV guide.
- Guide declares no channelsWithout <channel> elements there is nothing for a playlist to match against.