VAST error codes / Interactive and verification
VAST error 902: General InteractiveCreativeFile (SIMID) error
Short answer: A SIMID interactive creative loaded but failed at runtime. Introduced in VAST 4.1.
What it means
The `<InteractiveCreativeFile>` (SIMID) resource was found but could not run: the modern replacement for the VPAID 901 failure.
Common causes
- SIMID resource wrong `type` or `apiFramework`
- Interactive file unreachable
- SIMID runtime mismatch on the player
How to fix it
Validate the `<InteractiveCreativeFile>` type and apiFramework, and confirm the linear fallback plays without it.
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-interactive-creative-type: <InteractiveCreativeFile> should have a type attribute identifying the MIME type
- VAST-4.0-interactive-creative-no-api: <InteractiveCreativeFile> should have an apiFramework attribute
Related error codes
- VAST error 901: General VPAID error
- VAST error 409: Interactive unit not executed
- VAST error 410: Verification 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.