Hello-

I'm making calls to the V2 API using the bulk read on a report that's got over 1 million records in it.

I'm able to successfully request, check status and download the first batch of records. The response object header in the first batch comes with a recordCursor. I use that recordCursor to fetch the next batch of records, but the response from that subsequent request has the same exact recordCursor value in the Header. As a result, I can't move past the first batch! The documentation is unclear on how to use the record cursor, but I believe I'm using it correctly.

To summarize my steps:

- Create Bulk Read Job with access Token
- I'm getting the status of the bulk read job every 20 seconds until it becomes available (status=Completed). 
- Make a request using the /result endpoint. Get the recordCursor value from the response header.
- Make subsequent response to same /result endpoint, using the recordCursor value from the initial response in the request header.
- repeat the previous step until there is no recordCursor value in the header response.

The problem is this will go on forever because the recordCursor always exists and is always the same cursor string.

Thanks for any insight.