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 `ForecastService` and `AdjustmentService` are highlighted, with `ApiError` serving as a base. `DateError` is detailed, listing reasons like `DATE_IN_PAST`, `START_DATE_AFTER_END_DATE`, and `INVALID_DATES`. A vast array of specific error types are associated, such as `AdUnitCodeError`, `AuthenticationError`, and `QuotaError`. `ApiError` contains the error string, the data that caused the error, and field path information to identify the cause of the error. `DateError` has a reason field that describes the exact error.\n"]]
