VAST-2.0-duration-format
<Duration> value does not match HH:MM:SS[.mmm] format
ErrorValuesIAB VAST 2.0 §2.4.1VAST 2.0 and later (all versions)
VAST requires duration values to follow the `HH:MM:SS` or `HH:MM:SS.mmm` format. Plain English values like `"30 seconds"` or bare numbers like `"30"` are not valid and will cause players to fail to parse the duration.
How to fix
Rewrite the duration in HH:MM:SS format, e.g. 00:00:30 for 30 seconds or 00:01:30 for 90 seconds. Optionally append milliseconds: 00:00:30.500.
Invalid
<Duration>thirty seconds</Duration>Valid
<Duration>00:00:30</Duration>Check your VAST tag for
VAST-2.0-duration-format and other issues instantly.Validate a tag →Other Values rules
VAST-2.0-mediafile-delivery-enum<MediaFile> delivery must be "progressive" or "streaming"VAST-3.0-skipoffset-formatLinear skipoffset does not match HH:MM:SS[.mmm] or n% formatVAST-3.0-progress-offset-formatTracking progress offset does not match required formatVAST-3.0-skip-event-no-skipoffsetskip tracking event present but Linear has no skipoffset attributeVAST-3.0-minmaxbitrate-pair<MediaFile> must have both minBitrate and maxBitrate or neitherVAST-3.0-bitrate-conflict<MediaFile> has both bitrate and minBitrate/maxBitrateVAST-4.0-tracking-event-removedfullscreen/exitFullscreen tracking events were removed in VAST 4.0VAST-4.1-tracking-event-valueTracking event attribute not in the valid set for this VAST version