'Different lengths on ContinuationToken when calling Microsoft.Azure.Cosmos.ReadNextAsync
I have similar setup in three environments - the normal Test, QA and Prod.
Now in one environment, when calling ReadNextAsync against CosmosDb, the ContinuationToken has changed from a length of 140-150 to more than 5000.
I have dug through settings in Cosmos and my environments but have found nothing that would explain why Cosmos suddenly needs a much more complex ContinuationToken.
I noticed this because Cloudflare started returning 520.
One remedy would be to alter Cloudflare (not yet sure how)
but I'd prefer to have a shorter ContinuationToken since saving bits.
I have found no documentation how ContinuationToken is constructed.
ARandomDudeOnInternet removed a part of the ContinuationToken, which, at least at first glance, worked. But I don't trust hacking non-public stuff that I don't know how it works.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|