VAST error code
302 — Wrapper limit reached
What the spec says
The chain contained more wrapper redirects than the player allows, so resolution was abandoned.
What actually causes it
- A long supply chain where each intermediary adds its own wrapper.
- A player with a low wrapper limit — some CTV environments allow as few as three or four.
- A redirect loop, where a chain eventually points back at itself.
How to fix it
Count the hops by resolving the chain manually. If a loop exists it will be obvious. Otherwise this is a supply-path problem rather than a tag problem: shortening the chain is the only real fix, and it improves latency and match rate at the same time.
To see whether a tag would hit this before it runs, paste it into the VAST validator. It reads the XML and reports the conditions that map to this code.
Related codes
Code definitions from the IAB Tech Lab VAST 4.3 specification. Causes and fixes are practitioner guidance, last verified July 2026.