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 `ContentBundleService` and `NetworkService` handle API interactions, detailing potential errors through the `ApiError` inheritance. `ApiError` includes `fieldPath`, `fieldPathElements`, `trigger`, and `errorString` to pinpoint the cause. `RequestError`, a specific type of `ApiError`, is thrown due to user request issues and has a `reason` field with `UNKNOWN`, `INVALID_INPUT`, and `UNSUPPORTED_VERSION` enumerations. There are also many different error types that can be thrown, like `ApiVersionError` or `AuthenticationError`.\n"]]
