It's entirely possible this is just a Monday thing and my brain isn't quite working full-speed yet, but has anyone else noticed this stream position behavior?
Here are my steps:
1) First, I just did a GET to https://api.box.com/2.0/events
2) As expected, since I did not specify a stream_position, this returns a chunk of 100 very old events
3) Next, I grabbed the next_stream_position off the bottom of the result from step 1 and plugged it into my URL, like this: https://api.box.com/2.0/events?stream_position=creditcard
4) Hmm...still returns a chunk of 100 very old events
5) Try step 3 multiple new times (grabbing the next_stream_position each time) and always get the same result specified in step 4
6) Finally, tried to do a GET to https://api.box.com/2.0/events?stream_position=now
7) Results are much better - it's an empty collection of events
😎 Using the next_stream_position from step 6, do a GET like https://api.box.com/2.0/events?stream_position=creditcard
9) This also works great (returns an empty collection of events)
Take note of the diff between the next_stream_position returned via a "regular" GET of events (step 3: creditcard) and the next_stream_position returned via a "stream_position=now" GET of events (step 8: creditcard). This is a difference of 3,024,818,207.
Now, I know the stream_position moves ahead rapidly, but not THAT rapidly!
Has anyone else noticed this behavior, or is there something specifically borked in our account? My instinct is this is an issue that would effect all Box users, as it is my understanding the stream_position is universal system-wide.