Errors related to feature management. If you attempt using a feature that is not available to
the current network you'll receive a FeatureError with the missing feature as the trigger.
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 document outlines various services and potential errors within an ad management API, version v202502. Services include managing ads, content, creatives, targeting, forecasting, and reporting. It details a comprehensive list of service functionalities and their corresponding FeatureError references. The document then goes into the error structure, such as `ApiError`, `fieldPath`, `trigger`, and `FeatureError` that occurs when a service tries to use a feature that is not enabled, along with its possible reasons, such as `MISSING_FEATURE` or `UNKNOWN`.\n"]]
