Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples:"2014-10-02T15:01:23Z","2014-10-02T15:01:23.045123456Z"or"2014-10-02T15:01:23+05:30".
details
map (key: string, value: string)
Additional information about the error.
An object containing a list of"key": valuepairs. Example:{ "name": "wrench", "mass": "1.3kg", "count": "3" }.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis document describes the JSON representation of a user-facing error, structured with specific fields to convey error information.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ereason\u003c/code\u003e field provides a concise title explaining the error, while \u003ccode\u003eerrorUuid\u003c/code\u003e is a unique identifier for error tracking.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003emessage\u003c/code\u003e field contains detailed information about the error, and the \u003ccode\u003eerrorTime\u003c/code\u003e field records the error's occurrence time using RFC 3339 format.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003edetails\u003c/code\u003e field allows for a flexible map of key-value pairs to include extra information about the error that may be useful.\u003c/p\u003e\n"]]],[],null,["# Error\n\n- [JSON representation](#SCHEMA_REPRESENTATION)\n\nRepresent a user-facing Error."]]
