Failed request to Azure Cosmos DB service

Question

In Application Insights, we have traces indicate that an exception occurred while trying to add an entity document to CosmosDB.

The reason for the failure is that the service was unavailable (ServiceUnavailable) with a sub-status code of 20006.

If we look up ServiceUnavailable documentation, we can only find other sub-status codes. It is unclear what is sub-status code of 20006.

The following exception message contains information about the exception that was thrown: Inner exception message:

Something went wrong while writing the entity document to CosmosDB. Inner exception message: Response status code does not indicate success: ServiceUnavailable (503); Substatus: 20006; ActivityId: a92c6af4-359d-4348-8e78-5b2d85446283; Reason: (Channel is closed
ActivityId: a92c6af4-359d-4348-8e78-5b2d85446283, Microsoft.Azure.Cosmos.Tracing.TraceData.ClientSideRequestStatisticsTraceDatum, Linux/11 cosmos-netstandard-sdk/3.29.1);;

Answer 1

Thank you for sharing the document link. We have made updates to the document, and it now includes information on the Substatus Code=20006. You may view this information in the updated version of the document. Thank you.

Answer 2

Thanks for your question

This sub status seems to be related to Channel Closed

This happens when the connection between client and server is interrupted. This can happen in-cases either party terminates connection or connectivity between them is interrupted.

These failures are typically transient and retryable

Thank you!