Get Streams - Inconsistent response using "first" parameter

[BarryCarlyon]

Did this recently start happening or has it always done this.

It may be related to

Intermittent Error 400 (Invalid Cursor) from Helix Streams API

Around 12:30 PST I began seeing errors with pagination on the Helix Streams endpoint. Here is the response: Body: {"error":"Bad Request","status":400,"message":"invalid cursor"} Here was the chain of pagination before hitting the error: https://api.twitch.tv/helix/streams?first=100&type=all https://api.twitch.tv/helix/streams?first=100&type=all&after=ZXlKeklqbzVOakl5Tmk0MU5Ua3hNemszT1RreU1pd2laQ0k2Wm1Gc2MyVXNJblFpT25SeWRXVjkgZXlKeklqbzFNek0zTGpRNE1qSTFOakEwTWprME5pd2laQ0k2Wm1Gc2MyVXNJblFpT25Se…