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 2024-11-19 UTC."],[[["`HtmlBundleProcessorError` identifies errors during HTML5 file processing within Google Ad Manager."],["It encompasses various reasons for errors, such as file size limitations, invalid click tags, and unsupported file types like Flash."],["HTML5 bundles should not exceed 1000 KB in size and contain a maximum of 50 files, with one primary HTML file named `index.html`."],["This error ensures the quality and compatibility of HTML5 creatives served through Google Ad Manager."],["Errors are categorized by an enum `HtmlBundleProcessorError.Reason` with specific reasons like `FILE_SIZE_TOO_LARGE` or `CLICK_TAG_INVALID`."]]],["The document details error handling within the Ad Manager API, specifically focusing on `HtmlBundleProcessorError`. This error class inherits from `ApiError` and covers issues related to HTML5 bundles. Key problems include: inability to extract bundle files, hard-coded click tags, invalid click tags, primary HTML file issues, size or file count limits being exceeded, unsupported file types (like Flash), broken file references, invalid SVG blocks, and unparseable bundles. These errors are associated with the CreativeService and CreativeSetService.\n"]]