Music Added to running queue ignored

No, No, NO. I’m appalled that Sonos Support are still parroting this line as part of their standard boiler-plate advice. Gateway UPnP in a router has nothing to do with Sonos, and introduces a notorious point of network vulnerability. 

Returning to your issue, if a newly added ‘next’ track is throwing an error it’s almost certainly a network bandwidth issue. The track has to buffer in a hurry, to get going, and is probably running into packet loss problems when the stream chokes.

Same problem here, also with Spotify.

Add to queue next, will get skipped.
Add to end of queue and then move up to next, will get skipped.
Add two songs to queue next, the first one i skipped, the second is played.

If i go into queue and play the just skipped song, it will instantly play, no problem.

All my internet and network gear has been replaced for other reasons, i have loads of bandwidth, but this problem in Sonos has shown no change.
The skipped song can have 3 minutes or more to buffer while the already playing song finishes. It is still skipped. Hardly a problem with having to instantly buffer a song.

It seems to me, like a common denominator is Spotify.
Does anyone experience this with other streaming services?

Is the Spotify integration into Sonos, a Sonos issue or a Spotify issue?

I would be very interested in hearing, if someone has tried Spotify support?
Or if other streaming services also skips when you "add to queue as next"?
My Google-foo is coming up short.

Another thought:
When Move was new, there was a lot of problems with speaker groupings having to rebuffer and the likes of that.
It has gotten better, but i am somewhat unimpressed with the networking abilities of the Move.
I saw Move mentioned further up in the thread. Is this maybe a common denominator?

Regards Niels

@ntorlund 
I don’t use Spotify other than their free service, but I did try the things you mention with Deezer and Amazon Music services in the Sonos App.

I grouped together these rooms:

• Sonos Move called ‘Moveable’ (Group controller)
• Sonos Ones (gen1) paired, called ‘Utility’
• Sonos Ones (gen2) paired, called ‘Patio’

Then played a playlist and inserted a track into the queue using the ‘play next’ context menu option.

It all worked fine here..

One example from Amazon Music was I played a curated playlist called ‘All Hits U.K.’ and inserted (play next) a track called “Love (Sweet Love)” by Little Mix and it played it with no issues. Screenshot attached but this was just one of serveral examples I tried from both Music Services. So unless it’s a Spotify issue then I’m not seeing the issue you mention here. Hope that assists.

I'm seeing the same behaviour using the Spotify service through Sonos. Songs added with Play Next are skipped.

Selecting the song from the queue immediately after it has been skipped makes it play just fine.