mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #1090] sp.recommendations() randomly stopped working for no clear reason? #648
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#648
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 @KENSICKC on GitHub (Apr 26, 2024).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/1090
This code was working perfectly earlier, but it randomly stopped working. I have SPOTIPY_CLIENT_ID, SPOTIPY_CLIENT_SECRET, and SPOTIPY_REDIRECT_URI all defined as environment variables. When I run functions such as sp.current_user_top_tracks(), sp.artist(), and others, they all work fine.
When I run sp.recommendations(), nothing gets returned or printed; I get no error message, the program just hangs indefinitely. I have to restart visual studio to be able to run anything again. Again, I was having no issues with sp.recommendations() a few hours ago. I genuinely do not know what happened.
Thanks in advance
@dieser-niko commented on GitHub (Apr 27, 2024):
How often do you run that function? Might be a ratelimit
@JosepVargasf commented on GitHub (May 9, 2024):
Wow i have this same issue with the function "sp.track(track_id)" have you found a solution?
@KENSICKC commented on GitHub (May 9, 2024):
I did not find a solution unfortunately. I think it is a rate limit like dieser-niko said. If I stop running the function for 30-60 mins it starts working again.
@dieser-niko commented on GitHub (May 21, 2024):
I'm closing the issue as it seems that you found the problem. If you want to get an error message instead, just do the following: