This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 32%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPA%3C/text%3E%3C/svg%3E)
On April 9th, when I was testing the change feed via the Java SDK, the continuation token had EndTime fields in them with real timestamps. Now I am seeing timestamps that look like this: "+999999999-12-31T23:59:59.999999999-18:00" ?
The latter "timestamp" is preferable, because the token was coming back before with an EndTime that rendered it unusable. But why is it now behaving differently?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 57.00000000000001%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
@Papajohn, April ,
Thank you for sharing your findings with the community . It seems that the getEvents() function does lazy load of the events without any time range specification and hence the EndTime value comes as something which can be considered as infinity .
I just discovered why this is happening.
If I call BlobChangeFeedClient.getEvents(startTime,now) then the cursor that comes back will have an EndTime = now.
If I call BlobChangeFeedClient.getEvents(), then the cursor that comes back will have an EndTIme = +999999999-12-31T23:59:59.999999999-18:00