I have been having a very strange porblem. I use a mobile app to access the Document DB via a REST service. I am passing through the continuation token in the http headers. When the mobile client sends the first continuation token to me in a subsequent request, it works just fine, and I send over a new continuation token for the second page of results.
Now, things get interesting. I get zero results for the third page, even though I have a continuation token and I have verified that I have more than 40 records in the request. So, I changed the continuation token manually on the client side (I updated the number and the index in the continuation token) and sent it and in this scenario it works. I compared the continuation token sent by CosmosDB and the continuation token manipulated by me, and there's no difference. What could be the issue?
I have been having a very strange porblem. I use a mobile app to access the Document DB via a REST service. I am passing through the continuation token in the http headers. When the mobile client sends the first continuation token to me in a subsequent request, it works just fine, and I send over a new continuation token for the second page of results.
Now, things get interesting. I get zero results for the third page, even though I have a continuation token and I have verified that I have more than 40 records in the request. So, I changed the continuation token manually on the client side (I updated the number and the index in the continuation token) and sent it and in this scenario it works. I compared the continuation token sent by CosmosDB and the continuation token manipulated by me, and there's no difference. What could be the issue?