If this functionality is important for your deployments, create a support ticket in the Azure portal and the Azure Cosmos DB team will get back to you. Retry the multi-document transaction until it succeeds.Īdditional details should be provided in the error. The multi-document transaction failed due to a conflicting multi-document transaction Up to eight fields can be included in a compound index (compound indexes are supported in version 3.6+). Up to 500 single field indexes can be created in a container. The request to create an index cannot be completed.
#Robo 3t dark mode update#
Ensure that your request does not attempt to update that field or the shard key field. The request is attempting to change an immutable field
The document in your request did not contain the collection's shard key (Azure Cosmos DB partition key).Įnsure the collection's shard key is being used in the request. This will help you slowly delete data without impacting your production application. You can fetch a single document at a time and delete it through a loop. Use Cursor/Batch size to perform the delete. Consider using TTL (Based on Timestamp): Expire data with Azure Cosmos DB's API for MongoDB If you are trying to delete large amounts of data without impacting RUs: Retrying a write operation that has received this error may result in a duplicate write. In other cases, this error can be worked-around by splitting a large request into smaller ones. This can be solved by increasing the request units of that collection or database. One of the causes is when the currently allocated request units capacity is not sufficient to complete the request. The request has exceeded the timeout of 60 seconds of execution.
The database or collection being referenced in the query cannot be found.Įnsure your database/collection name precisely matches the name in your query. The request lacks the permissions to complete. Retry the multi-document transaction or limit the scope of operations within the multi-document transaction to make it complete within the 5 second time limit. The multi-document transaction surpassed the fixed 5 second time limit. The query requests a sort on a field that is not indexed.Ĭreate a matching index (or composite index) for the sort query being attempted. One common cause is that an index path corresponding to the specified order-by item is excluded or the order by query does not have a corresponding composite index that it can be served from. Therefore, some of these errors are only found in Azure Cosmos DB's API for MongoDB. It provides an implementation of the MongoDB wire protocol version 4.0, 3.6, and legacy support for wire protocol version 3.2. Azure Cosmos DB does not host the MongoDB engine.