> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/publishers/vast/vast-errors.md). # VAST Errors The following list explains all the errors that a VAST Inline or a VAST Wrapper might return to the HTML5 Video Player: | Code | Description | | ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 100 | XML parsing error. | | 101 | VAST schema validation error. | | 102 | VAST version of response not supported. | | 200 | Trafficking error. Media player received an Ad type that it was not expecting and/or cannot play. | | 201 | Media player expecting different linearity. | | 202 | Media player expecting different duration. | | 203 | Media player expecting different size. | | 204 | Ad category was required but not provided. | | 205 | Inline Category violates Wrapper BlockedAdCategories (refer 3.19.2). | | 206 | Ad Break shortened. Ad was not served. | | 300 | General Wrapper error. | | 301 | Timeout of VAST URI provided in Wrapper element, or of VAST URI provided in a subsequent Wrapper element. (URI was either unavailable or reached a timeout as defined by the media player.) | | 302 | Wrapper limit reached, as defined by the media player. Too many Wrapper responses have been received with no InLine response. | | 303 | No VAST response after one or more Wrappers. | | 304 | InLine response returned ad unit that failed to result in ad display within defined time limit. | | 400 | General Linear error. Media player is unable to display the Linear Ad. | | 401 | File not found. Unable to find Linear/MediaFile from URI. | | 402 | Timeout of MediaFile URI. | | 403 | Couldn’t find MediaFile that is supported by this media player, based on the attributes of the MediaFile element. | | 405 | Problem displaying MediaFile. Media player found a MediaFile with supported type but couldn’t display it. MediaFile may include: unsupported codecs, different MIME type than MediaFile\@type, unsupported delivery method, etc. | | 406 | Mezzanine was required but not provided. Ad not served. | | 407 | Mezzanine is in the process of being downloaded for the first time. Download may take several hours. Ad will not be served until mezzanine is downloaded and transcoded. | | 408 | Conditional ad rejected. (deprecated along with conditionalAd) | | 409 | Interactive unit in the InteractiveCreativeFile node was not executed. | | 410 | Verification unit in the Verification node was not executed. | | 411 | Mezzanine was provided as required, but file did not meet required specification. Ad not served. | | 500 | General NonLinearAds error. | | 501 | Unable to display NonLinearAd because creative dimensions do not align with creative display area (i.e. creative dimension too large). | | 502 | Unable to fetch NonLinearAds/NonLinear resource. | | 503 | Couldn’t find NonLinear resource with supported type. | | 600 | General CompanionAds error. | | 601 | Unable to display Companion because creative dimensions do not fit within Companion display area (i.e., no available space). | | 602 | Unable to display required Companion. | | 603 | Unable to fetch CompanionAds/Companion resource. | | 604 | Couldn’t find Companion resource with supported type. | | 900 | Undefined Error. | | 901 | General VPAID error. | | 902 | General InteractiveCreativeFile error. code | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.exoclick.com/publishers/vast/vast-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.