On-demand MPD asks to be refreshed
A static manifest declares minimumUpdatePeriod, which contradicts type="static".
What it means
type="static" says the manifest will never change, while @minimumUpdatePeriod asks players to re-fetch it. Both are present.
Why it matters
Players honouring the update period will re-request a manifest that never changes, adding pointless load on your origin for the whole duration of every session. It is usually left over from a template shared with the live workflow.
How to fix it
- Remove minimumUpdatePeriod from static manifests.
- If the manifest genuinely does change, it should be type="dynamic" instead.
Check your own stream
The free DASH validator runs this check on every analysis and links each finding straight back here.
Open the DASH validator →Frequently asked questions
- What does "On-demand MPD asks to be refreshed" mean?
- type="static" says the manifest will never change, while @minimumUpdatePeriod asks players to re-fetch it. Both are present.
- Why does it matter?
- Players honouring the update period will re-request a manifest that never changes, adding pointless load on your origin for the whole duration of every session. It is usually left over from a template shared with the live workflow.
- How do I fix it?
- 1. Remove minimumUpdatePeriod from static manifests. 2. If the manifest genuinely does change, it should be type="dynamic" instead.
- Can a validator catch this before viewers do?
- Yes. The free DASH MPD validator checks this on every run, together with UTCTiming, clock drift and segment addressing — the live problems that only appear on other people's devices.
- What is the first thing to try?
- Remove minimumUpdatePeriod from static manifests.
Related DASH checks
- DASH manifest has no UTCTiming elementA live MPD without UTCTiming forces players to trust the device clock, so any skew on the viewer’s machine becomes stalls or missing segments.
- DASH availabilityStartTime is in the futureThe manifest claims the presentation starts later than the current time, so no segment is available yet and playback cannot begin.
- The DASH manifest is not well-formed XMLThe document could not be parsed as XML, so nothing else could be checked.
- The document has no MPD root elementThe XML parsed, but its root is not <MPD>, so it is not a DASH manifest.
- MPD declares no profileWithout @profiles a player cannot tell which DASH feature set the manifest expects.
- MPD declares no minBufferTimePlayers use this required attribute to size the initial buffer before starting playback.