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?