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."],[],["This document outlines various services within an ad management API, including `AdRuleService`, `AdjustmentService`, `CreativeService`, `ForecastService`, and `NetworkService`, among others. It details a hierarchy of errors, beginning with `ApiError`, then going down to `ServerError`, detailing specific types like `AuthenticationError`, `InternalApiError` and `QuotaError`. `ServerError` contains `SERVER_ERROR`, `SERVER_BUSY`, and `UNKNOWN` as its reasons, indicating server-side issues. It also defines `ApiError` fields like `fieldPath` and `trigger`.\n"]]
