Error 429, retry-after missing

[SemyD]

So i have been working on an app for the past fiew days. I am now doing some testing for rate limits but the problem is i'm unable to see the retry-after time in the response when i get the error 429. So i can't do anithing about it and no matter how long i wait for it to reset it's never reset. So i am kinda stuck. Anyone has some clues on how i can fix that?

[theofficialneff]

Same here, I can access the header when making calls to the genre endpoint, but not for audio-features or audio-analysis. Very frustrating.

[FreddyE1982]

I got the same problem with audio-features and audio-analysis. I am now basically locked out of those endpoints.

[Thajobe]

Hi
I've the same problem for the audio-analysis.
For the audio-features I've not hit the rate limit, as one can request it for multiple tracks at once.
But it is annyoing, that we have no clue how often we can sent an audio-analysis, especially if you can only request one analysis at once.

How are we supposed to handle the 429 Error in this case? Or what rate limit applies for audio-analysis requests?

[gahivelvel]

I am seeing the same issue where I'm getting 429 responses without actually getting a Retry-After header. This was working properly before but they seem to have gone missing.

For me this is now happening on the GetArtist endpoint (https://developer.spotify.com/documentation/web-api/reference/get-an-artist).

[jdrui]

Any solutions? Or anybody can update how long they waited for the rate limits to be refreshed? I just had the same thing. I could still access 'playlist_items' but not 'audio_features' (which I was able to an hour ago).

[Thajobe]

I found that a related bug for some ids can cause a similar bug.
See topic:
https://community.spotify.com/t5/Spotify-for-Developers/Strange-error-for-some-spotify-ids-on-audio-...

[Blueblakk]

Facing the exact same issue where the multiple audio-features endpoint returns 429 but does not seem to give us back the "retry-after" header, unlike the other endpoints. 😞

[1Dr490n]

I have the same problem, but with track 

[tonzbird]

I am also having this issue now with a dataset that was fine previously

[glenn_mcdonald]

Same problem here, in my case with the related-artist endpoint. I'm trying to obey the rate-limits, but with no Retry-After I have no idea how long to wait!

[glenn_mcdonald]

This is still an ongoing problem. With no Retry-After my app has no way to know how long to wait, and is thus hitting rate-limits and getting banned. Retry-After is the solution to this: you tell me how long to wait, I diligently do so. If you don't include Retry-After, the relationship is dysfunctional!

[simdev]

I am receiving the Retry-After header, but it's always 1. Not helping at all.