VAST Error 302: Wrapper limit reached
The chain has more nested wrappers than the player allows — usually more than 5 hops — and the player refused to follow further.
Every player caps wrapper depth to protect itself from infinite chains; the VAST spec suggests 5 as a sane maximum and most players enforce something close to it. Error 302 means the chain was still handing off to another wrapper when the cap was hit.
Deep chains are a structural symptom: each hop is a middleman reselling the impression. Beyond the error itself, every hop adds latency (see 301) and takes a revenue share.
Why error 302 happens
Daisy-chained resellers
SSP A fills from SSP B who fills from network C who fills from DSP D — each adds a wrapper. Programmatic resale chains grow hops organically.
Circular demand paths
Two exchanges buying from each other create chains that grow until the depth cap stops them — the cap is doing its job.
Unnecessary internal wrapping
Some ad servers wrap even their own direct demand in an extra redirect layer for tracking, burning a hop for no decisioning value.
How to fix VAST error 302
- 1
Count the hops
Resolve the chain and count wrappers before the inline ad. Anything above 3–4 deserves scrutiny hop by hop.
- 2
Identify who each hop is
Map each VASTAdTagURI domain to the partner behind it. Hops that add no unique demand are pure margin-takers — cut them.
- 3
Negotiate more direct paths
Supply-path optimization: buy or sell through the shortest route to the actual demand. Fewer hops means fewer 302s, fewer 301s, and better margins.
- 4
Check for loops
If the same domain appears twice in one chain, you have a circular resale path — flag it to both partners immediately.
Seeing error 302 on a live tag?
Paste the tag URL or XML — the validator resolves the full wrapper chain, validates the schema, downloads every media file, and shows exactly which stage fails.
Validate your VAST tagVAST error 302 — frequently asked questions
How many wrappers is too many?+
The spec's guidance and most player defaults land at 5. Practically, chains longer than 3 hops start losing meaningful revenue to timeouts even before hitting the depth cap.
Can I raise the player's wrapper limit to fix 302?+
If you own the player, sometimes — but it treats the symptom. A deeper chain is slower, more fragile, and pays more middlemen. Shortening the chain is nearly always the better fix.
Does each wrapper hop take a revenue cut?+
Usually yes — most hops exist because an intermediary is reselling the impression at a margin. Depth caps are as much an economics problem as a technical one.