Getting sane errors out of sprocs about azure-cosmos-dotnet-v3

[kentcb]

Thanks @mkolt - this is great.

Per my original request though, I don't think this issue should be closed until this information has been added to the docs. I just tried googling "Cosmos DB SubStatusCode errorCode" and can't find anything in the docs about this. Actually, one of the first results to come up is this user voice.

[kirankumarkolli]

@kentcb can you please sent a mail to askcosmosdb[AT]microsoft.com? I will compile and put the summary on this thread.

[mkolt]

From inside sproc you can throw new Error(errorCode, "Error message"), where errorCode is a number (short int) like 1234. On client side you can get this code from DocumentClientException as SubStatusCode which can be obtained from DocumentClientException.ResponseHeaders (e.g. see how to get it).

[andersborum]

What's the status on this? I am unable to find any official information on the "x-ms-substatus" HTTP response header. I've been using Cosmos DB for some time now and am starting to write SPROCs using typescript (async/await for the win), and with that quickly came the requirement of relaying different error codes back to the caller.

[AlejandroBlanco]

I agree. This is poor or forced design. Error codes within errors throws from sprocs cause always a BadRequestException without any data except a cosmosError added by force to suck Exception and the internal sub error codes. I think the container client should parse the error codes, not the user