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.
Inspect the wrapper chain first
VAST error 302 is a wrapper-chain failure. Inspect each hop, then test the resolved tag.
What your player reported
302· Wrapper limit reached, as defined by the media player. Too many Wrapper responses have been received with no InLine response.
Wording from the IAB VAST 4.3 specification error table. Players may shorten or reformat it, but the code is the same.
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
- VAST-2.0-wrapper-depth: Wrapper chain depth exceeds the configured maximum
Related error codes
- VAST error 300: General wrapper error
- VAST error 301: Wrapper timeout / URI unreachable
- VAST error 303: No ads after wrappers
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