Are there any error messages?

The error message I always receive is "unable to add songs to the queue"

How big is the playlist? How long does it take between you trying to play it, and the error? (I’m going to guess exactly 10 or 20 seconds).

It's a fairly big playlist, yes it takes about 10 seconds til the error shows up. 

Its too big then, you’ll need to split it up (using the Spotify app).

Thanks!  Was hoping for a different answer can always play via Bluetooth vs splitting the playlist.  Any idea if this will ever change?  It’s a poor CX in my humble opinion.

That’s difficult to predict. How many tracks are there in the playlist?

2.2K songs.  An “everything” list

The average length of a streaming Music track is around 3m-30s according to various articles online, including this website…

https://www.measuringknowhow.com/find-out-what-is-the-average-length-of-a-song-in-the-us/

So that playlist will play for a total in excess of 128 hours 33 minutes

Thats rather a lot - here’s a suggestion:

If you split the playlist into perhaps two halves (or more) as an example, you can begin playing the first half to your Sonos room(s) and then simply add the second half of the playlist to the end of the same playing queue - and all should play and stay in situ, until you change the queue, or reboot/update your speaker/group controller device. 

Hope that assists and it’s likely going to be much better quality audio than using playback of the entire larger playlist over Bluetooth.

Thanks for the assistance!

The problem is that the Sonos app tries to load the entire playlist into the queue, and 10 seconds is not enough time for larger lists. Possible fixes from Sonos would be:

1. Increase the timeout, but then starting playback will take ages for large playlists
2. Not grabbing the whole playlist in one gulp, but getting it in chunks (each chunk < 10 seconds)
3. #2 plus starting playback after the first chunk

To be fair Sonos do recommend that music services limit their containers to 500 items for this very reason, but no-one does because that’s a worse problem IMHO.

I have tried implementing #2 as an experiment in my Windows app, but loading the queue is the blockage and I’m only seeing a 50% success rate, plus it takes ages.

File names and meta data size play a large role in the maximum tracks in playlists and the Queue. Here’s a playlist that I cooked up and loaded into the Queue. There is sill some room in the Queue for adding a few more tracks.

Next I added a small music playlist to the Queue. We are not yet at the end of the road. The absolute limit would be 65,000 tracks for the Queue.

The Queue size limit (65535) is not the issue here though, the problem is the loading time from the music service and the speed with which those items can be added to the queue. Plus the playlist Buzz is loading appears to be a Sonos one, which is a very different beast to a music service one (the playlist and the queue are on the same device, no network calls required).

Orthogonal: I find queue updates are one of the most brutal events to handle in the app, as it is challenging to figure out how to efficiently update the UX without having to reload the entire queue, and to do it quickly enough that you can handle the next queue update message in a timely fashion.