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 details error handling within several services, including `AudienceSegmentService`, `ForecastService`, `LineItemService`, `OrderService`, `ProposalLineItemService`, and more. It specifies the `AudienceSegmentError`, outlining potential issues when dealing with audience segments. Errors are categorized with reasons such as invalid rules, unsupported segment types, name conflicts, policy violations, and incorrect custom criteria. `ApiError` provides common error information like field path and trigger, inherited by `AudienceSegmentError`, which defines segment-specific error reasons.\n"],null,[]]