I know this topic is very old but we are seeing the same issue showing up in our application recently. Has anyone gained more insight into what causes this / how to work around it?
Interestingly it looks like this is a sporadic issue because issuing the exact same request will sometimes produce the correct data and other times will return incorrect data.
Would love to hear from Twitter on this