VAST Error 206: Ad break shortened — ad was not served
The ad break was cut short and this ad's slot disappeared before it could play — a pod-level scheduling drop, not a broken ad.
In CTV and live streams, ad breaks sometimes shrink after the pod was already filled — the content resumes early, the break gets truncated by the stitcher, or a live event returns from break ahead of schedule. Ads whose slots vanished report 206.
The creative, the tag, and the chain are all typically fine. This code exists so sellers can distinguish "the ad was fine but the break ended" from genuine delivery failures.
Why error 206 happens
Live content returned early
Live sports and news breaks have unpredictable lengths. When the program resumes, remaining pod slots are dropped.
Server-side stitcher truncated the pod
SSAI systems assemble pods against a time budget; timeouts or re-planning mid-break can cut trailing slots.
User skipped or exited the break
Skippable formats and app navigation can end a break before later pod positions play out.
How to fix VAST error 206
- 1
Check whether 206 clusters on late pod positions
If drops concentrate on the last slots of long pods, the pod length exceeds what the content's breaks reliably support — shorten the pod.
- 2
Review stitcher timeout budgets
SSAI pod assembly that runs close to its time budget truncates under load. Tighter upstream timeouts leave headroom for every slot.
- 3
Treat residual 206 as normal in live
Some volume is inherent to live programming. Monitor the rate; investigate only when it spikes or shifts position patterns.
Seeing error 206 on a live tag?
Paste the tag URL or XML — the validator resolves the full wrapper chain, validates the schema, downloads every media file, and shows exactly which stage fails.
Validate your VAST tagVAST error 206 — frequently asked questions
Does a 206 count as a billable impression?+
No. The ad never rendered, so no impression fired. 206 exists precisely to explain the gap between ads returned and impressions counted.
Why did 206 only appear after VAST 4.1?+
Earlier versions had no code for pod truncation, so these drops were reported as 900 (undefined) or not at all. 4.1 added it alongside the ad-pod features that made the situation common.