Expose ScriptLog on CosmosException

When execution of a stored procedure fails, it would be useful to be able to see the script log. However, even though it’s exposed on StoredProcedureResponse<T>, it’s not exposed on CosmosException.

Describe the solution you’d like A ScriptLog property on CosmosException.

Describe alternatives you’ve considered The script log is accessible from the headers, but it’s not very convenient, because you need to remember the header name, and manually escape the value:

var scriptLog = Uri.UnescapeDataString(ex.Headers["x-ms-documentdb-script-log-results"] ?? string.Empty);

Additional context N/A

[j82w]

I think the best option would be to expose a CosmosStoredProcedureException : CosmosException with the additional property. Adding it to the base exception doesn’t make since with it only returning for a single API in the SDK.

@thomaslevesque what is the reason you are using stored procedure instead of Transactional Batch or Bulk?

[thomaslevesque]

Please reopen. The issue is still relevant, inactivity or not.