Getting a 502 bad gateway when trying to read /me/tracks

[derwish]

Plan

Premium

Country

Belarus

Device

PC

Operating System

Windows 10

My Question or Issue

Description:
I have about 135,000 saved tracks in my library and I can't get a list of them.
Everything worked until there were not many saved tracks.
I can see the list of tracks in the desktop app. But the list is not displayed in the web player. After a long wait, it tells me that the playlist was not found.
Also, I cannot get the list using API Console (/me/tracks). I get the "502 Bad Gateway Error" in response.

Try to get /me/tracks for my user_id.

Endpoint(s):

GET /v1/me/tracks

Scope(s):

user-library-read

Steps to reproduce:
- Add 135,000 saved tracks
- Open the API Console
- Call the Get Current User's Saved Tracks endpoint /me/tracks

Expected behaviour:

Some data

Actual behaviour:

502 Bad Gateway Error

[spotifyjosh]

What an impressive music collection, @derwish!

Are you seeing the 502 error response from every request that you make to /me/tracks? Or does the request succeed some of the time for you?

[derwish]

This happens on every request. The list of my tracks is never available either through the api or in the web player.

[scottonspot]

I am having this same problem. I can get my user info from /me, but /me/tracks consistently gives 502 errors.

[scottonspot]

@spotifyjosh I tested the other /me endpoints and they all work except for /me/tracks and /me/albums, which both consistently return 502: Bad gateway.

[scottonspot]

The 502 error occurs even in the Spotify Developer console

[Soch]

Did you manage to solve this?

I'm having the same issue with my app, it works well for every user, except for one that has 19k saved tracks. Seems like the API returns a 502 when there are too many tracks. 

Perhaps with an offset it works?

[scottonspot]

Last time I tried I had the same problem. I don’t think adding an offset changes anything; that /tracks endpoint just always fails. Very annoying.