Daniel Scott-Raynsford

Hi @jamie-tillman - good catch and thanks for raising this. `$ProgressPreference` should be supported here. I'll see what is going on and submit a fix this weekend.

I'm having trouble identifying the cause of this. If I place a `Write-Verbose -Message ("Progress Preference = $ProgressPreference") -Verbose` right before the call to Invoke-WebRequest in `Invoke-CosmosDbRequest` then it does...

Hi @tkumark - I'll take a look at this and see if I can find any issues with it. Sorry about the delay.

What I think I'll need to do here is catch this exception and bubble it up with a more useful message. I could try and prevent the SQL from being...

Good idea @jasonchester. Suggest we could extend the existing `Remove-CosmosDbDocument` function with a `-Query` parameter instead of implementing a new function. Within the Remove-CosmosDbDocument function it might call out to...

The following list of custom exceptions need to be implemented and handled: https://docs.microsoft.com/en-us/rest/api/cosmos-db/http-status-codes-for-cosmosdb

Good idea @Szeraax. This could be handled in a similar way way to how 429's are handled: https://github.com/PlagueHO/CosmosDB#how-to-handle-exceeding-provisioned-throughput Are you talking about specific error types (e.g. timeouts)?

The `New-CosmosDbBackoffPolicy` won't retry indefinitely if you specify a `-MaxRetries` (although I should have named it `-MayRetry` - which at some point I'll alias). It does also implement support for...

One thing I'd also add is that the 429 back off policy method would still need to work as is, because of the need to deal with the `x-ms-retry-after-ms` -...

Hi @sdg002, Can you try the following query: ```powershell $queryForCount="SELECT VALUE COUNT(1) FROM docs c" ``` and see if that works?