[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-05 UTC。"],[[["\u003cp\u003eSuccessful Firestore in Datastore mode requests return an HTTP \u003ccode\u003e200 OK\u003c/code\u003e status code with the requested data.\u003c/p\u003e\n"],["\u003cp\u003eFailed requests return an HTTP \u003ccode\u003e4xx\u003c/code\u003e or \u003ccode\u003e5xx\u003c/code\u003e status code and an error response containing \u003ccode\u003ecode\u003c/code\u003e, \u003ccode\u003emessage\u003c/code\u003e, and \u003ccode\u003estatus\u003c/code\u003e fields.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003estatus\u003c/code\u003e field within error responses represents the canonical error code, crucial for classifying and understanding the nature of the error.\u003c/p\u003e\n"],["\u003cp\u003eThe content type of the request (\u003ccode\u003eapplication/x-protobuf\u003c/code\u003e or JSON) will determine the structure of the error in response, with the \u003ccode\u003ecode\u003c/code\u003e field being different depending on the content.\u003c/p\u003e\n"],["\u003cp\u003eSpecific error codes, such as \u003ccode\u003eABORTED\u003c/code\u003e, \u003ccode\u003eALREADY_EXISTS\u003c/code\u003e, or \u003ccode\u003eDEADLINE_EXCEEDED\u003c/code\u003e, provide detailed reasons for failure and guide appropriate actions like retrying or fixing the request.\u003c/p\u003e\n"]]],[],null,["# Errors and Error Handling\n\nWhen a Firestore in Datastore mode request is successful, the API will return an HTTP\n`200 OK` status code along with the requested data in the body of the response.\n| **Note:** The errors and status codes described in this page are returned by the low-level Datastore API. Note that client libraries may or may not return these same values.\n\nWhen a request fails, the Datastore API will return an HTTP\n`4xx` or `5xx` status code that generically identifies the failure as well as a\nresponse that provides more specific information about the error(s) that caused\nthe failure.\n\nThe rest of this page describes the structure of an error, enumerates specific\nerror codes, and recommends how to handle them.\n\nThe following is the structure of an error response for a JSON request: \n\n {\n \"error\": {\n \"code\": \"integer\",\n \"message\": \"string\",\n \"status\": \"string\"\n }\n }\n\nThe response object contains a single field `error` whose value contains the\nfollowing elements:\n\nHere's an example of an error response for a JSON request: \n\n {\n \"error\": {\n \"code\": 400,\n \"message\": \"Key path is incomplete: [Person: null]\",\n \"status\": \"INVALID_ARGUMENT\"\n }\n }\n\nIf a request made with a content type of `application/x-protobuf` results in an\nerror, it will return a serialized [`google.rpc.Status`](https://github.com/googleapis/googleapis/blob/master/google/rpc/status.proto) message as the\npayload.\n| **Note:** The text provided in the message could change at any time so applications should not depend on the actual text.\n\nError Codes\n-----------\n\nThe recommended way to classify errors is inspect the value of the\n[canonical error code](https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto) (`google.rpc.Code`). In JSON errors, this code appears\nin the `status` field. In `application/x-protobuf` errors, it's in the `code`\nfield."]]
