401's on some, not all, search API calls

[runtbob]

I have an app that maintains a ranking of my most played songs over certain periods. I get this ranked list from last.fm, which does not have direct links to the spotify URIs, so I make calls to the /search endpoint for each song in order to get a URI. I send around ~100 of these requests each time I update the playlists, with handling in case I get rate-limited.

What's strange is that despite them all using the same authorization token, a few of those requests will return with a 401, even on app start when the access token was just generated. Is anyone else experiencing this? I'm going insane.

I am using Axios to make the calls. Seems to matter in a lot of the threads I've read through.

[ReubenF]

Yeah, I'm seeing this as well:

• https://github(.)com/Matatika/tap-spotify/actions/runs/10349125516/attempts/1
• https://github(.)com/Matatika/tap-spotify/actions/runs/10349125516/attempts/2
• https://github(.)com/Matatika/tap-spotify/actions/runs/10349125516/attempts/3
• https://github(.)com/Matatika/tap-spotify/actions/runs/10366175198/job/28694848290