![]() ![]() When using Customer-Managed Keys (CMK) in Azure Cosmos DB, if there are any errors, Azure Cosmos DB returns the error details along with an HTTP substatus code in the response. This situation could happen due to network connectivity or service availability issues. The operation could not be completed because the service was unavailable. The operation failed due to an unexpected service error. This code only occurs on write operations. The operation encountered a transient error. Retry the request after the server specified retry after duration. The collection has exceeded the provisioned throughput limit. This status code indicates that the current operation was considered failed because of another failure within the same transactional scope. When a document operation fails within the transactional scope of a TransactionalBatch operation, all other operations within the batch are considered failed dependencies. The throughput scale operation cannot be performed because there is another scale operation in progress. The document size in the request exceeded the allowable document size for a request. Retry the request after reading the latest version of the resource and updating the eTag on the request. The operation specified an eTag that is different from the version available at the server, that is, an optimistic concurrency error. For partitioned collections, ID must be unique within all documents with the same partition key value. Use another ID for the resource to resolve this issue. The ID provided for a resource on a PUT or POST operation has been taken by an existing resource. ![]() This code is returned when a stored procedure, trigger, or UDF (within a query) does not complete execution within the maximum execution time. The operation did not complete within the allotted amount of time. For example, the resource may have already been deleted. The operation is attempting to act on a resource that no longer exists. Direct REST client must perform GET on DatabaseAccount to identify the current write region and forward the write request to that endpoint. ![]() This status code is used as a redirection code by drivers to forward the write requests to a new write region. 403.3 – This status code is returned for write requests during the manual failover operation. Any requests originating from machines outside the allowed list will receive a 403 response. ![]() 403 forbidden error is returned when the firewall rules configured on your Azure Cosmos DB account block your request. 403 can also be returned when a stored procedure, trigger, or UDF has been flagged for high resource usage and blocked from execution. An example of this scenario is when you try to add documents to a collection that has reached its provisioned storage. 403 code is also returned during a POST operation to create a resource when the resource quota has been reached. 400 is also returned when a request that requires an x-ms-documentdb-partitionkey does not include it.Ĥ01 is returned when the Authorization header is invalid for the requested resource. 400 is also returned when the consistent level for a GET operation is overridden by a stronger consistency from the one set for the account. In addition, a 400 can also be returned when the required properties of a resource are not present or set in the body of the POST or PUT on the resource. The JSON, SQL, or JavaScript in the request body is invalid. POST on a stored procedure resource to execute the stored procedure.Ī POST operation to create a resource is successful. One of the following REST operations were successful: - GET on a resource. This article provides the HTTP status codes returned by the REST operations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |