VAST error codes / Interactive and verification
VAST error 901: General VPAID error
Short answer: A VPAID interactive unit failed to load or run.
What it means
The creative used VPAID and the interactive unit errored. VPAID is deprecated and unsupported on most CTV and modern environments.
Common causes
- VPAID creative on a player without a VPAID runtime (most CTV)
- Missing or wrong `apiFramework="VPAID"`
- Empty or unreachable VPAID JS URL
How to fix it
Migrate VPAID creatives to SIMID plus OMID. vastlint flags VPAID usage and points to the migration path.
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-vpaid-apiframework: apiFramework="VPAID" is deprecated as of VAST 4.1
- VAST-4.1-vpaid-in-interactive-context: VPAID MediaFile alongside InteractiveCreativeFile — VPAID unsupported in CTV
Related error codes
- VAST error 902: General InteractiveCreativeFile (SIMID) error
- VAST error 409: Interactive unit not executed
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.xmlUse 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.