VASTlint

VAST error codes / Wrapper errors

VAST error 302: Wrapper limit reached

Short answer: Too many wrapper hops with no inline ad before the player's depth limit.

What it means

The chain redirected through more wrappers than the player allows without ever reaching an `<InLine>` response.

Common causes

  • A long redirect chain across multiple ad servers
  • A wrapper loop that never terminates in an inline ad
  • A player depth limit lower than the chain length

How to fix it

Shorten the chain or raise the limit if the chain is legitimate. Use the inspector to count hops and spot loops.

VAST error codes are runtime buckets emitted by the player. They tell you where the failure happened, not which line of XML caused it. Paste the raw tag into the validator to map this code onto the exact element and rule.

Related vastlint rules

Related error codes

Debug this tag now

Validate the XML, follow the wrapper chain, or check it in CI before launch:

# CLI: exits non-zero on errors, ideal for pipelines
vastlint check creative.xml

Use the right tool for this failure

If you already have the resolved XML, run a pure spec check. If you only have a live tag URL, test that endpoint first. If the failure happens in the wrapper chain, inspect each hop.

Validate this XML →Test this live URL →Inspect this wrapper chain →

Further reading