Resolve VAST and IMA SDK errors

You can create a VAST errors report in Query Tool. More information about these errors are shown here and in the VAST specification to help you troubleshoot and resolve issues.

Non-logged drop-offs

If you see a greater than 25% difference between your total code served count and ad impressions, it's likely due to non-logged drop-offs. These can be caused by user, site, or player latency or crashes, users leaving the page before the player has a chance to play the ad, or request prefetching.

If they're due to prefetching, this is expected and no action is necessary. However, player and site issues should be investigated as a possible solution.

Severity levels of video errors

A video player can trigger some errors, but still play the ad. These errors are considered "non-fatal" warnings. Other "fatal" errors often cause the video ad to stop the request for the failed ad and either request another ad, or resume playback of the video content. Behavior varies by player implementation.

Error indicator Indicates a fatal error, which likely stopped the ad request.
Warning indicator Indicates a non-fatal warning, which may have continued to play the ad.

Expand all Collapse all

VAST errors

Error indicator    100     VAST XML parsing error

Likely cause of a VAST 100 error

This can be caused when the buyer's response is either malformed or an otherwise invalid XML document, or a redirect VAST URL that fails to resolve successfully.

Recommended action

  Publisher Alert the buyer.
Buyer Verify that the VAST XML is correctly formatted and contains all of the required elements and attributes. You can learn more in the VAST specification from the IAB.
Error indicator    101     VAST schema validation error

Likely cause of a VAST 101 error

This can be caused when the buyer's response is missing required elements or attributes of the XML or contained unrecognized elements, according to the IAB standard.

Recommended action

  Publisher Alert the buyer.
Buyer Verify that the VAST XML is correctly formatted and contains all of the required elements and attributes. You can learn more in the VAST specification from the IAB.
Error indicator    102     VAST response version not supported

Likely cause of a VAST 102 error

This can be caused when a video player does not support the VAST version specified in the bid request.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that only supported VAST versions are sent in a response.
Error indicator    200     Video player expected different ad type

Likely cause of a VAST 200 error

This can be caused when a video player does not expect or support an ad type requested in a bid request. For example, if a skippable ad is sent when a player is only configured to support linear ads, or if a skip offset is longer than expected. 

Recommended action

  Publisher Check for trafficking errors or alert the buyer.
Buyer Ensure that only specified ad types are sent in a response, and that skippable linear creatives respect the skip offset attribute.
Warning indicator    201     Video player expected different linearity

Likely cause of a VAST 201 error

This can be caused when the linearity in the buyer's response does not match the video player's request. For example, if a non-linear ad was sent in a response when a linear ad was specified in the request.*

Recommended action

  Publisher Ensure that the correct linearity is specified in the ad request.
Buyer Ensure that the response only includes linearity specified in the request.

* Ad Exchange RTB only supports linear ads. 

Warning indicator    202     Video player expected different duration

Likely cause of a 202 VAST error

This can be caused when the creative returned is a different duration than specified. For example, a creative of duration 30 seconds is returned, but the actual MediaFile duration is 60 seconds.

Recommended action

  Publisher Ensure that the creative duration is set properly in Ad Manager.
Buyer Ensure that the response respects the max duration specified in the request.
Warning indicator    203     Video player expected different size

Likely cause of a VAST 203 error

This can be caused when a buyer's returned MediaFiles are incompatible with the device from which the bid request is sent. It often occurs when high bitrate creatives are returned to mobile devices. 

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that your response includes MediaFiles that are compatible with different technologies and devices, including bitrates.
Error indicator    300     Wrapper error

Likely cause of a VAST 300 error

This is a general wrapper error and is not actionable.

Error indicator    301     VAST redirect timeout reached

Likely cause of a 301 VAST error

This can be caused when a VAST redirect tag does not return a response within the timeout (5 seconds is the default) specified in a wrapper element. It could include request errors, such as an invalid URI, unreachable or request timeout for a URI, security, or other exceptions related to requesting a VAST URI. It could also be due to a high latency connection (for example, 3G) or simply a slow response from a buyer.

Recommended action

  Publisher Increase the timeout limit of your player via the SDK. Learn more
Buyer Ensure that the VAST redirect URI is reachable and no protocol issues exist (for example, responses hosted on HTTP and served to an HTTPS site.
Error indicator    302     Wrapper limit reached

Likely cause of a 302 VAST error

This can be caused when the wrapper limit defined by the video player is reached. Either too many wrapper responses are received without an inline response, a circular loop of daisy chaining exists (one network bouncing to another and another), or too many empty VAST responses from video fallback.

Recommended action

  Publisher Increase the wrapper limit of your player via the SDK. Learn more
Buyer Verify that any VAST redirects are not redirecting again to another network. When too many redirects are called from a video player before a valid MediaFile is returned, the player might abort the ad request.
Error indicator    303     Empty VAST response returned

Likely cause of a 303 VAST error

This can be caused when no ads are returned in a VAST response after one or more wrappers. This also includes empty VAST responses from video fallback.

When working with third-party networks, the fill-rate can be less than 100%. If so, this is an expected error. For example, if the third-party expects to fill 60% of the time, you should expect 40% errors.

Recommended action

  Publisher Ensure that the error rate is in line with the fill-rate of the third-party network. Video fallback may be helpful to avoid losing impressions.
Buyer Ensure that bids are not being returned with an empty VAST response, and that empty responses are not being returned by the advertiser or agency hosting the creative.
Error indicator    400     General linear error

Likely cause of a 400 VAST error

This can be caused when a video player is unable to display the linear ad. It may occur when the MediaFile is not a valid video file of the specified format, or because the browser restricted autoplay with sound, or another unknown reason.

Recommended action

  Publisher Check for player issues, enable your player to detect for restricted autoplay, or alert the buyer.
Buyer Ensure that the VAST response returns a valid creative.
Error indicator    401     MediaFile not found

Likely cause of a 401 VAST error

This can be caused when a file cannot be found from a MediaFile URI.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that all MediaFile URIs in the VAST response return a valid video creative.
Error indicator    402     Unable to download or timeout of MediaFile URI

Likely cause of a 402 VAST error

This can be caused by a problem fetching or playing the MediaFile, and could be any of the following:

  • The loadVideoTimeout is set too low in the IMA SDK. The default is 8 seconds.
  • Low bandwidth or poor website implementation with competing requests that delay loading of the MediaFile.
  • A video auto-plays in a mobile environment, whereas it should be click-to-play (there are some exceptions).
  • Showing video ads in an auto-play environment (for example, a playlist), while the window is not in focus (either another tab is selected, or window is minimized).*

For players that use the IMA SDK, video fallback may be helpful to avoid losing impressions.

Recommended action

  Publisher Increase the timeout limit of your player via the SDK. Learn more
Buyer Ensure that any CDN-hosted creatives are returned within the specified media timeout.

* Only happens in the Chrome web browser. 

Error indicator    403     VAST response declared unsupported MIME types for all MediaFiles

Likely cause of a 403 VAST error

This can be caused by a VAST response that declares unsupported MIME types for all available MediaFiles (for example, Flash on mobile, or WebM on iOS). It may indicate that the wrong creative type attempted to play.

This error type is more common on mobile.

Recommended action

  Publisher Ensure that the creative format or technology requested is supported by the video player's device and platform. For example, VPAID creatives should not be requested from mobile apps.
Buyer Ensure that all returned creatives respect the video format in the bid request.
Error indicator    405     MediaFile display error

Likely cause of a VAST 405 error

This can be caused when a faulty creative is returned. Creatives can fail due to a mismatch between the MIME type and the video file type, a CORS configuration on the creative’s CDN, or other transcoding-related reasons.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that all creative MIME types and CDN configurations are accurate. 
Warning indicator    406     Missing required mezzanine file

Likely cause of a VAST 406 error

This can be caused a VAST response is returned without a required mezzanine file. Publishers with server-side ad implementations often require mezzanine files, which are raw high-quality video files for ad-stitching, or to generate video files of appropriate quality.*

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that a mezzanine file is included in your response when required by the publisher.

* This is a feature of VAST 4

Error indicator    407     Mezzanine file downloaded for the first time

Likely cause of a 407 VAST error

This can be caused when the mezzanine file is downloaded for the first time, so no ad is served. It can also occur when an ad insertion is missed because the creative is being transcoded. It continues to occur until the creative is available for insertion.*

Recommended action

This is expected while the video is being transcoded and no action is required.

* This is a feature of VAST 4

Error indicator    408     Rejected ad in VAST response

Likely cause of a 408 VAST error

This can be caused when the ad returned in the VAST response is rejected.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that only approved creatives are returned in your VAST response, or that any advertisers or agencies hosting the creatives are aware of rejections.
Error indicator    409     Interactive creative defined in the InteractiveCreativeFile node did not execute

Likely cause of a 409 VAST error

This can be caused when a creative defined in the InteractiveCreativeFile node does not execute.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that any interactive creatives returned in your response successfully play when requested.
Error indicator    410     Code referenced in the Verification node did not execute

Likely cause of a VAST 410 error

This can be caused when the code referenced in the AdVerification node does not execute.*

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that the verification code referenced in the response is correctly implemented according to the verification vendor.

* This is a feature of VAST 4 

Error indicator    500     General NonLinearAds error

Likely cause of a VAST 500 error

This can be caused when a video player is unable to display a non-linear ad, for an unknown reason.

Recommended action

  Publisher Check for video player issues or alert the buyer.
Buyer Ensure that the VAST response returns a valid creative.
Error indicator    501     Non-linear ad creative dimensions do not align with creative display area

Likely cause of a 501 VAST error

This can be caused when a non-linear ad is unable to play because the creative dimensions did not align with creative display area (the creative dimension was too large). It may occur if you use CSS styles to set width and height of the video content element.

Recommended action

  Publisher Ensure that the set width and height match the display area. If you set the width and height of the video content element with CSS styles, set them with HTML attributes instead.
Buyer Alert the publisher.
Error indicator    502     Unable to fetch NonLinearAds/NonLinear resource

Likely cause of a VAST 502 error

This can be caused when the buyer's response returns a non-linear ad that fails to return a valid creative.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that valid creatives are returned in the non-linear ad response.
Error indicator    503     Could not find NonLinearResource with supported type

Likely cause of a VAST 503 error

This can be caused when the publisher requests a creative size that is larger than the video player size, or an invalid media type.

Recommended action

  Publisher Ensure that requested creative sizes and media types are acceptable for the video player.
Buyer Alert the publisher.
Warning indicator    600     General CompanionAds error

Likely cause of a VAST 600 error

This can be caused when a publisher is unable to display a companion ad, for an unknown reason.

Recommended action

  Publisher Check for ad serving issues, or alert the buyer.
Buyer Ensure that the VAST response returns a valid creative.
Warning indicator    601     Companion creative dimensions did not align with companion display area

Likely cause of a VAST 601 error

This can be caused when the companion creative dimensions do not fit within the companion display area.

Recommended action

  Publisher Ensure that the requested companion ad size fits within the dimension of the ad unit from which the request is made.
Buyer Alert the publisher.
Warning indicator    602     Unable to display required companion

Likely cause of a VAST 602 error

This can be caused the publisher is unable to render the companion ad creative returned in the VAST response.

Recommended action

  Publisher Check for ad serving issues, or alert the buyer.
Buyer Ensure that the VAST response returns a valid creative.
Warning indicator    603     Unable to fetch CompanionAds/Companion resource

Likely cause of a VAST 603 error

This can be caused when the buyer's response returns a companion ad that fails to return a valid creative.

Recommended action

  Publisher Alert the buyer.
Buyer Ensure that valid creatives are returned in the companion ad response.
Warning indicator    604     Could not find Companion resource with supported type

Likely cause of a VAST 604 error

This can be caused when a publisher requests an unsupported creative type for the companion ad slot.

Recommended action

  Publisher Ensure that specified creative types are supported for the companion ad slot.
Buyer Alert the publisher.
Warning indicator    900     VAST 2 error

Likely cause of a 900 VAST error

This can be caused when any VAST 2 error occurs, even if VAST 3 is requested or your network default is set to VAST 3.

Recommended action

  Publisher Either begin to request VAST 3 or enable VAST 3 for your network. *
Buyer Work with the publisher to troubleshoot the exact issue, or respond with VAST 3.**

  * Query Tool reports an aggregate of 900 errors. This type of 900 error is much more common than a 900 Undefined VAST 3 error.
** RTB Breakout does not report on this type of 900 error, because it is almost always a non-fatal warning.
     For 900 errors reported in RTB Breakout, see 900 Undefined VAST 3 error.

Error indicator    900     Undefined VAST 3 error

Likely cause of a 900 VAST error

This is the result of an unknown VAST 3 error, which likely stopped the ad request.

Recommended action

  Publisher Alert the buyer.*
Buyer Work with the publisher to troubleshoot the exact issue.**

  * Query Tool reports an aggregate of 900 errors. This type of 900 error is much less common than a 900 VAST 2 error.
** Of the two types of VAST 900 errors, this is the only type that is reported in RTB Breakout.

Error indicator    901     General VPAID error

Likely cause of a 901 VAST error

This can be caused by any VPAID error, which could be any of the following:

  • SSP VPAID wrapper not buying
  • SSP VPAID wrapper timeout
  • VPAID creatives required insecure mode
  • An Ad Exchange "IMA Adapter" tag is used with the IMA SDK, and a VPAID ad is returned (the "Direct SDK" tag should be used)

Recommended action

  Publisher Ensure that any VPAID creative requests are supported for devices and players. You can use video creative profiles to control which creatives are eligible to serve.
Buyer Ensure that any VAST responses that return HTML5 VPAID wrappers from IAS/DV/MOAT include an MP4 asset, and that the wrapper is not aborting playback. Also, ensure that you don't bid on impressions without a determined advertiser or buyer, or attempt to initiate a client-side resale.

IMA SDK errors

These errors are not part of the VAST specification.

Error indicator  1005     URI malformed

Likely cause of a 1005 IMA SDK error

This can occur when either the encoding or decoding of a URI was not successful.

Recommended action

  Publisher Ensure that any special characters in your URI strings are encoded correctly.
Buyer Alert the publisher.
Was this article helpful?
How can we improve it?