"Failed to return owned playlists for the current user."

Amazon Music
1

Hi!
We got an error HTTP 500 “Failed to return owned playlists for the current user.” while trying to retrieve user playlists for some Amazon Music customers.
Here is the request: https://api.music.amazon.dev/v1/me/playlists?limit=100

Do you know why we have such an error for only a few users and what it means? @sam

I also tried for a specific customer to retrieve only his public playlists with the dedicated endpoint and got this error:

“Request to MusicPlaylistService API getPlaylistsByIdV2 failed due to exceeding the timeout of 3000ms”

It’s like there’s a big playlist in the list or at least a specific playlist that is failing the whole retrieve process. Let me know if you need the customer ID.

Thank you.

2

Thank you for bringing this to our attention.
We did find a couple of these service timeouts in our logs and are now investigating.

1 Like
3

That’s great! We are still having the issue.
Do you have some updates?

4

Hi Thomas,

still working on it. There is a chance we might be decreasing the maximum value for “limit” in order to avoid these timeouts.
Could you lower that value on your end for now (e.g. from “100” to “50”) and check if you are still experiencing these errors?

5

Hi!
Thank you for the update.

The issue is probably unrelated to pagination, as I still have the error for some users, even when setting a limit to 50 and even trying with 1 or 2.

6

Hi!
Unfortunately, we still have this error message for some users.
Are there any updates on this?

Best,
Thomas

7

@Marco Hi!
We still have the error “Failed to return owned playlists for the current user.” from time to time.
Any updates?

Thank you.

8

Hi @Thomas !
My team has identified the root cause for these timeouts and has been planing for a service udpate. I’ll check with them to get an ETA. Thanks for your patience and following up.

1 Like
9

Hi!
Have you been able to get an ETA?
Thank you.

10

Hi Thomas,

the team has deployed a service update about 4 weeks ago, but I believe I am still seeing this error pattern in our logs. Has the frequency of these errors changed on your end in any way?

11

Good to know!
I still experience it multiple times per day; it could be less, yes, but it’s hard to tell (we no longer have logs for previous months). The issue is still present, unfortunately.