A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-20 UTC."],[],["This document details errors associated with HTML5 file processing within ad management services. Key actions include processing bundles and extracting files, with specific restrictions on file sizes (under 1000 KB), quantities (under 50 files), and types (no Flash). Errors arise from issues like missing primary HTML files, invalid click tags, unsupported components or properties, broken links, or decoding failures. These are classified as `HtmlBundleProcessorError` with specific `reasons` such as `CLICK_TAG_INVALID` or `FILE_SIZE_TOO_LARGE`.\n"]]