I suspect you’re hitting the regular Sonos queue-loading timeout, perhaps because Spotify is slow to respond. Weekend evenings could be the peak of server demand.

The desktop controller interaction you describe would execute as thousands of single-track queue additions, each of which would obviously complete in a fraction of the normal timeout period.

It is independent of time or day, and it does this consistently - i.e. it throws the error every single time. 

If it had to do with server load, I would expect it to be hit or miss.

I tried adding "My liked songs" to a Sonos playlist, to see if that would work. Adding directly threw a similar error, but saving the Sonos queue as a Sonos playlist works. I can then play the Sonos playlist without problems. I'm assuming that is because the references to the tracks have then been stored in the system and don't need to be fetched from Spotify on the fly.

I'll use that as a workaround for now, but I hope this gets fixed, because there doesn't appear to be anything I can do myself to fix this.

Sonos does indeed store the URIs in a Sonos Playlist. I routinely use an 8k+ track Sonos playlist, of which about 50% are Amazon Music tracks. It loads into the queue instantly.

Loading playlists from a service itself always tends to be subject to limits, whether it be maximum size or a timeout. I used to use Deezer where the practical playlist max size to stay within the timeout limit was around 1-1.5k. Amazon won’t load more than 500 tracks from a playlist come what may.

Hi!

Same issue for me as well since recent days/ weeks. Unable to play a large (2.5K songs) Spotify playlist.

My workaround was to split the large playlist into parts of 1K songs and then add them one by one to queue via Sonos app.

Don't know where the problem is: is it Sonos's Spotify module or the Spotify services lag, but some weeks before it worked for me well. 

/Alexey.

Glad to hear I'm not the only one. Sorry, I accidentally marked your post as "best answer" when I wanted to like it.

*Moderator edit...removed the “Best Answer” flag*

Hi @Sjoop1985 

Thanks for your post!

Which room(s) are you having this issue in? Keuken in particular is having problems with interference. I recommend a read of our help page Reducing wireless interference.

Do you have the same issue if you try to play to your ethernet-wired Beam? If so, what is it ethernet-wired to? If it’s wired to a Google mesh node, is it the main node?

Finally, how close to the Beam is the Sub?

Sorry, I didn't see this reply until now.

I have this issue with every single room, wired or not. As I mentioned in the OP,  nothing has changed in my network or in the wireless environment, as far as I know (and as far as I can do anything about). My network matrix has looked the same for years, including some interference here and there that never caused much issue.

Wired speakers Beam and Arc are wired to the main node (router) of a Google WiFi system. Sub is bonded to the Arc and sits about 2 ft from the Arc, next to the cabinet the Arc is on (not sure how this is relevant).

And, as mentioned: this used to work ever since I started using Sonos, until 2 weeks or so ago, similar to what @Alexey Sharayev is reporting.

In my case, I have two houses with sonos,  and the issue is for both homes. I cannot add to queue a Spotify playlist of 2,5K songs in both my networks.

This occurring in two different houses, to me, more or less demonstrates that it is not related to interference or network issues. My suspicion is that it's somehow related to the Spotify/Sonos integration.

Hi @Sjoop1985 

If this is happening to your wired devices then it clearly has nothing to do with interference - seeing as the wired units are wired to the main node.

When rebooting your network, did you leave things unplugged for at least 30 seconds? If not, I recommend you try this.

Failing that, the only likely issue I can see relates to which device is acting as the STP root bridge. We can alter this by telling a wired unit to act in that regard instead of the Google mesh. Please visit http://192.168.86.105:1400/advconfig, set FirstZP to Enabled and click Submit. Once done, please reboot Kantoor.

If this doesn’t help, I recommend you get in touch with our technical support team, for some real-time troubleshooting.

I hope this helps.

I will try this, but the setup has been like this with Google Wifi as the STP root bridge since 4 years before this issue occurred.

Also interesting that another user is having this same issue since recently, on two different Sonos households. I appreciate the help trying to find a problem with my setup, but I get a feeling this is not hardware/config related.

Didn’t see a clear resolution here—I’ve been having a similar problem.

My most frequent method of adding tracks to the Sonos queue is to shuffle my Liked Songs from Spotify (about 2k tracks). This used to work fine until ~3 weeks ago.

Now, I cannot even add a single track from my Liked Songs without getting the 701 error. If I choose the exact same song from a different playlist, then it works fine. So it’s not just the shuffling/adding of 2,000 songs at once…there seems to be some malfunction when it comes to queuing anything from Spotify Likes.

 I’ve tried all the standard troubleshooting, including logging out and re-authorizing my Spotify account within the Sonos app.

Sonos recommend music services do not offer up Collections with more than 500 items, for this very reason:

https://developer.sonos.com/build/content-service-add-features/add-play-shuffle-all/

“In containers with many playable items (500+) this can cause a delay while the Sonos player processes the request. Sonos may even time out and give the listener an error. We recommend limiting the number of playable items in these types of containers as a palliative measure.”

I'm amazed by the quote above from Sonos. Normally, I've always been nothing but positive, but this is a pretty severe usability issue. I use the Spotify "my liked songs” feature to curate my complete music library, independent of artist, album or genre and sometimes I just want to shuffle through that.

I remember that years ago, people with large music libraries (above Sonos’ track limit) were always told that the future was streaming, but now we're getting similar limitations there?

The quote also doesn't explain why I could add almost 3000 tracks without problems up to 2 months ago...

Maybe something has slowed down, either your connection to Spotify (eg its picking a different CDN or network route) or some local network condition.

The timeout is ten seconds I think, and if that used to take 9 seconds, but now takes 11 seconds, then that would be enough for a failure now.

Sonos could theoretically fix this by using paging in this scenario: the doc I linked specifically says it does not use paging, though it doesn’t say why.

Weeks I have been struggling with the error code “An error occurred while tracks to the queue (701)” from selecting the ‘Liked Song’ within the Sonos app.

If I copy 1-2-1 to a playlist there is no problem. With another playlist or Albums there isn’t a problem.

Playing from Spotify and connect to my speaker isn’t a problem. 

​​​​​​​+ there is a second account of my partner, and she hasn’t that problem at all.

On another location the Spotify Liked songs within the Sonos app works without any problem.

<My setup>

>beam + x 2 Play 1] → wired connection → one room (tv setup)

nPlay 3] → wireless connection → one room 

�Roam roam] 

<Troubleshoot>

contacted the helpdesk and did the following steps.

• Remove my account from the Sonos App (mobile and desktop version) & added it again. Even removed the app and reinstall.
• Reboot my network + Sonos + added all my services. (Did it probably 5 times) 
• Changed my DNS. 
• Changed the channels of the Sonos mesh 

{outstide the sonos environment}

• went to my Spotif account logged out everywhere.  
• changed my Spotif password
• Check my geolocation (credit card & account related address) 

casenumber: 04313898

any help is welcome! 

Same problem here since approx 1,5 months. Always used to use “my liked songs” directly in every room without problems. Just opened the app selected the room and pressed shuffle in “my liked songs” (“nummers” in dutch) and done.

Now i always encounter the 701 error. The work around mentioned above works for me, but is a slow process (only works when using my windows app (select all songs and drag them into the queue window which starts a slow adding songs process). My list contains more than 2500 songs, but was never ever a problem (it still isnt a problem when i drag all the songs in the queue). Even double clicking 1 song only in the most right window of the windows app gives me a 701 error, but dragging 1 song to the middle window (the queue part of the app) doesnt give me a problem.

This dragging songs workaround can only be done on a computer and doesnt work in an android phone, so once you lose your “liked songs” list in a room you need to use the slow workaround again on a computer.

This also works (not the way and less than ideal btw): open spotify on your phone > play “liked songs” > dive into settings and select the room you want. In this way you dont use the sonos app at all. I use remote buttons from ikea to start my music with normally and want every room pre-loaded with my liked songs, this doesnt work the way it should anymore.

Please help us and fix this.

Im pretty sure nobody changed anything in their network (i know i havent). This really seems to be a combination problem between sonos+Spotify.

These problems seemed to pop up like 6 weeks ago approx for everyone above. Change it back please :)

Helpppp

One more less related thing. Not all songs in spotify have the same volume, within spotify itself you can check a function thats called something like “normalize volume”, but we cannot use this feature within sonos, this causes awkward situations sometimes. can this function be added in the future somehow?

But yes:

HELP pls

I was having the same issues after I updated last night. I also have worked hard involving a half dozen playlists with the “liked songs” being the ones I enjoy the most at that particular time. In my case my Son and his family were here on a vacation and I recalled he used his phone to pull up his music. Upon that revelation I checked the settings on my iPad and noticed my Sonos settings had both Bluetooth and network settings on. I turned Bluetooth off and I again was able to play my liked songs. I hope this may help others solve a very frustrating problem for music enthusiasts like myself.