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-08-06 UTC."],[],["The core content outlines error handling for HTML5 file processing within a service. It details the `HtmlBundleProcessorError` and its various reasons, such as issues with extracting files, incorrect click tags, file size or quantity limits, unsupported file types (e.g., Flash), missing or multiple primary HTML files, and more. The `ApiError` and its related fields like `fieldPath`, `trigger` and `errorString` are the base class from which other errors are derived, and are the framework for how the errors are structured.\n"],null,[]]