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."],[[["\u003cp\u003eThis documentation details the \u003ccode\u003eServerError\u003c/code\u003e for the \u003ccode\u003eCustomTargetingService\u003c/code\u003e within the Google Ad Manager API.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eServerError\u003c/code\u003e arises from issues related to the server, encompassing unexpected errors or high server load.\u003c/p\u003e\n"],["\u003cp\u003eIt provides a structured way to understand server errors through fields like \u003ccode\u003ereason\u003c/code\u003e, \u003ccode\u003efieldPath\u003c/code\u003e, and \u003ccode\u003eerrorString\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ereason\u003c/code\u003e field further categorizes the error using an enumeration like \u003ccode\u003eSERVER_ERROR\u003c/code\u003e, \u003ccode\u003eSERVER_BUSY\u003c/code\u003e, or \u003ccode\u003eUNKNOWN\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can use this information to diagnose and address server-related problems encountered when interacting with the CustomTargetingService.\u003c/p\u003e\n"]]],["The document outlines various services and their associated server errors within the Google Ad Manager API (v202411). It lists services like `AdRuleService`, `AdjustmentService`, `CreativeService`, and many others, detailing each service's potential `ServerError`. The `ServerError` includes the error reason, it can be `SERVER_ERROR`, `SERVER_BUSY`, or `UNKNOWN`. It also shows that `ApiError` is inherited and the document details that it has `fieldPath`, `fieldPathElements`, `trigger`, and `errorString` properties.\n"],null,[]]