Can you provide the code you're running that produces this error?

Sure! You can reproduce by simply creating a BigQuery job stream with startIndex. It will work for the first request and start at the right startIndex, then throw if there's a second page to be fetched in the result set because the library also forwards pageToken in addition to startIndex and the server doesn't accept both (which makes sense).

const job = new BigQuery(...).createJob(...);
const stream = job.getQueryResultsStream({ startIndex: 2000 });

for await (const row of stream) { // throws on the second page
  // ...
}

Since the library forwards the pageToken cursor parameter on the second request, startIndex becomes obsolete. Therefore, if we use a pageToken from a server response, we can simply discard startIndex.

Hey @steffnay, any progress on this? We currently have to run a fork and would like to get back on the bandwagon at some point :)