Error 500 for matches for player 'Asmir'

Pretty much as the topic states. Hitting the matches for player endpoint for gamertag ‘Asmir’ consistently returns 500.

Works fine for me

Now it works fine for me too, but previous it was erroring for a long tine. Perhaps it returns 500 until some kind of initial condition is hit - like checking the player on waypoint? idk

> 2533274903705983;3:
> Now it works fine for me too, but previous it was erroring for a long tine. Perhaps it returns 500 until some kind of initial condition is hit - like checking the player on waypoint? idk

If noticed that if you requests a players history very quickly AND out of order, you can get 500 errors.

For example; If you know a player has 500 matches played, and you pre-build the 20 request required to parse their entire match history. If you fire these requests off with no regard for the sequence (i.e. not necessarily having request for matches 1-25 first, 26-50 second), the out of sequence queries will fail. I suspect they timeout.

Is this familiar?