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 and their associated server errors within an ad management API, version v202411. It lists services like `AdRuleService`, `AdjustmentService`, `AudienceSegmentService`, and others, detailing potential `ServerError` types for each. It also specifies inheritance relationships, showing `ApiError` and `ServerError` as core error types. `ServerError` reasons include `SERVER_ERROR`, `SERVER_BUSY`, and `UNKNOWN`, indicating unexpected errors, high server load, or undefined values respectively. The document lists the ApiError's fields, including `fieldPath`, `fieldPathElements`, `trigger` and `errorString`.\n"]]