type ServerError (v202408)
Stay organized with collections
Save and categorize content based on your preferences.
Errors related to the server.
- Namespace
-
https://www.google.com/apis/ads/publisher/v202408
Field
|
ApiError (inherited)
|
fieldPath
|
xsd:string
The OGNL field path to identify cause of error.
|
fieldPathElements
|
FieldPathElement[]
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.
|
ServerError
|
reason
|
ServerError.Reason
Enumerations
-
SERVER_ERROR
- Indicates that an unexpected error occured.
-
SERVER_BUSY
- Indicates that the server is currently experiencing a high load. Please
wait and try your request again.
-
UNKNOWN
- The value returned if the actual value is not exposed by the requested API version.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-06 UTC.
[null,null,["Last updated 2025-08-06 UTC."],[[["\u003cp\u003eThis documentation details the \u003ccode\u003eProposalService\u003c/code\u003e and the potential errors, specifically \u003ccode\u003eServerError\u003c/code\u003e, you might encounter when using the Google Ad Manager API.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eServerError\u003c/code\u003e arises from server-side issues, like unexpected errors or server overload, hindering proposal operations within Ad Manager.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation provides a detailed breakdown of \u003ccode\u003eServerError\u003c/code\u003e, including its namespace, inheritance hierarchy, fields, and potential reasons for its occurrence, aiding in troubleshooting and resolution.\u003c/p\u003e\n"],["\u003cp\u003eIt encompasses comprehensive information on fields like \u003ccode\u003efieldPath\u003c/code\u003e, \u003ccode\u003etrigger\u003c/code\u003e, and \u003ccode\u003eerrorString\u003c/code\u003e inherited from \u003ccode\u003eApiError\u003c/code\u003e, along with the specific \u003ccode\u003ereason\u003c/code\u003e field for \u003ccode\u003eServerError\u003c/code\u003e, offering insights into the nature of the error.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can leverage this information to understand and address server-related errors, ensuring smooth proposal management within their Ad Manager integrations.\u003c/p\u003e\n"]]],["The content details various services and their associated server errors within the Ad Manager API (v202408). It lists services like AdRuleService, AdjustmentService, and many others, including ProposalService. The \"Inheritance\" section outlines error types such as ApiError, AudienceSegmentError, and ServerError. ServerError has specific reasons like SERVER_ERROR, SERVER_BUSY, and UNKNOWN. Key actions involve handling errors based on the listed services and understanding error types for troubleshooting. Fields to identify cause of error are provided.\n"],null,[]]