VAST error codes / Interactive and verification
VAST error 410: Verification unit not executed
Short answer: An AdVerifications (OMID) unit failed to run. Introduced in VAST 4.1.
Debug this tag now
If you only have a live URL, test it first. If the failure is in the wrapper chain, inspect each hop. Validate resolved XML when you already have the response.
What your player reported
410· Verification unit in the Verification node was not executed.
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 player found `<AdVerifications>` but the verification (OMID) resource did not execute.
Common causes
- Verification resource unreachable or wrong type
- Missing `vendor` or `<JavaScriptResource>`/`<ExecutableResource>`
- OMID not supported on the player
How to fix it
Check each `<Verification>` has a vendor and a usable resource. Validate the AdVerifications block in vastlint.
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-4.1-verification-vendor: <Verification> is missing required vendor attribute
- VAST-4.1-verification-no-resource: <Verification> should have JavaScriptResource or ExecutableResource
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