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 details various services within an ad management system, including `AdjustmentService`, `AudienceSegmentService`, `LineItemService`, and others, for a total of 24 services. Additionally, it outlines the inheritance of `ApiError`, branching into numerous specific error types like `AuthenticationError`, `ForecastError`, and `QuotaError`, totaling 64 error types. The core data fields within the `ApiError` include `fieldPath`, `fieldPathElements`, `trigger`, and `errorString`, used to identify error causes. `TypeError` itself being a distinct error.\n"]]
