CODEWITHSUNDEEP
azure-cosmosdb
Xander
Xander

Reputation: 9171

CosmosDB Intermittent 503 errors

I am getting intermittent 503 errors on cosmosDB. They don't happen very frequently, but I'm wondering how I can resolve them. I have cosmosDB setup serverless, and I was wondering if in part that might be the root of the problem.

Response status code does not indicate success: ServiceUnavailable (503); Substatus: 20002; ActivityId: 3e5e8b5e-6672-401a-af01-3f046d5a6b81; Reason: (Response status code does not indicate success: ServiceUnavailable (503);

Upvotes: 1

Views: 505

Answers (1)

Mark Brown
Mark Brown

Reputation: 8783

SubStatus 20002 is typically caused by client-side timeouts.

Next step is to troubleshoot why your SDK client instance is timing out. More details here, Troubleshooting client side timeouts.

Upvotes: 1

Related Questions