mirror of
https://github.com/alexk218/tagify.git
synced 2026-04-27 04:15:49 +03:00
[GH-ISSUE #28] Experiencing 429 "Too Many Requests" Error When Using Tagify with Spotify API #3
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tagify#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kevincho26 on GitHub (Dec 23, 2025).
Original GitHub issue: https://github.com/alexk218/tagify/issues/28
Hi! I’ve been running into an issue with Tagify in Spotify where I keep getting a 429 - Too Many Requests error when trying to tag tracks. Despite following the Retry-After instructions in the header, the error persists. Here’s what I’ve tried so far and the results.
Issue Details:
When I try to tag a single track (e.g., https://api.spotify.com/v1/tracks/{id}), I receive a 429 error even after waiting for the time indicated in the Retry-After header.
The Retry-After value varies between 15 and 60 seconds, but even after waiting the suggested time, I still get the 429 error.
I’ve tried switching networks (using mobile hotspot), but the error continues. I also tried using a different Spotify account and VPN, but it didn’t fix the issue.
I’ve set up a rate limit guard in my Spicetify configuration to handle the 429s, but Tagify still crashes because it doesn’t handle the API errors properly (specifically when trying to parse undefined and encountering a .map error when attempting to process the data).
What I’ve tried:
Installing Tagify and enabling it correctly with Spicetify.
Updating and modifying the rate_limit_guard.js file to throttle requests properly.
Waiting between 15 and 60 seconds as per the Retry-After value, but the 429 error persists.
Using a different network (mobile hotspot) and trying a new Spotify account.
Disabling Tagify and testing Marketplace to see if the issue still happens, but it continues.
Technical Details:
I’m using Spotify version 1.2.77.358.
Spicetify version 2.42.7.
Tagify version installed from the official repository
.
The issue doesn’t seem to be just about making too many requests. I’ve confirmed that it’s also related to how Tagify handles the 429 error. When this happens, Tagify attempts to process an undefined response and crashes with a .map error.
What Happens:
Console Error:
TypeError: Cannot read properties of undefined (reading 'map')
This error occurs because Tagify doesn’t properly handle the 429 response, causing it to try accessing undefined data.
I just want to be able to tag tracks without hitting the 429 error.
I was hoping Tagify could better handle the 429 error, by waiting for the Retry-After time and retrying properly without crashing.
Steps to Reproduce:
Open Spotify and enable Tagify with Spicetify.
Try to tag any track (for example, a known track ID).
Notice the 429 error appears, with the Retry-After header respected but the problem still persists.
@alexk218 commented on GitHub (Dec 23, 2025):
Hey! Thanks for the detailed write up.
Funnily enough I actually just ran into this problem myself, I'm currently 429'd...
The fact that we're having this problem at the same time is interesting...
Need to confirm the cause.
How long have you been having this issue for?
It's possible Spotify tightened up rate limits on specific endpoints. I'll need to handle API requests better.
I'll be optimizing all of Tagify's API calls. There are a lot of ineffiencies and 429 is not properly handled.
I'll keep you posted on any developments. Thank you.
@Kevincho26 commented on GitHub (Dec 23, 2025):
For me everything was working perfectly up until Sunday. Since yesterday (when I opened Tagify again), I started getting 429s consistently. Even after waiting hours (I tried multiple long breaks, including ~3 hours), the restriction still doesn’t seem to clear — I can hit a 429 even when tagging a single track.
So it really feels like something changed on Spotify’s side (possibly tighter limits on /v1/tracks or related endpoints), rather than my setup.
Thanks again for the great work on Tagify. I’ll keep an eye on updates, and if the restriction suddenly clears on my end or I find anything useful, I’ll report back here.
Cheers!
@alexk218 commented on GitHub (Dec 23, 2025):
It's strange that these 429s are persisting so long.
Backing off completely would be a good idea - making more requests at this point will likely increase the time that we're rate limited. Next Tagify update will have optimized API calls.
Thanks for keeping me posted!
Cheers
@alexk218 commented on GitHub (Jan 8, 2026):
Solved! Check the latest release.
I think you guys will love the new features as well :) Let me know what you think!
@Kevincho26 commented on GitHub (Jan 8, 2026):
I'm testing it right now, everything seems to be working perfectly. Thank you very much and keep up the incredible work!
@alexk218 commented on GitHub (Jan 8, 2026):
Awesome!!! This makes my day.
Thank you for being an early supporter. Lots of exciting stuff coming up, stay tuned!