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 content outlines various services, including Company, Contact, Network, Order, PublisherQueryLanguage, and User services. It details the inheritance structure of errors, with `ApiError` as the base, branching into specific errors like `InvalidEmailError`. `InvalidEmailError` is triggered by an invalid email address and defines the reason for failure as `INVALID_FORMAT` or `UNKNOWN`. Key fields associated are `fieldPath`, `fieldPathElements`, `trigger`, and `errorString` from `ApiError`, and `reason` from `InvalidEmailError`.\n"]]
