Yup!

No. But that sure sounds like a duplicate IP address issue, where the Sonos system is fighting for network connections at times.

Try powering down all Sonos devices, then reboot your router. Give the router a couple of minutes to come back up, then power on your Sonos devices.

If the issue continues, submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

 I have no duplicate IP Address issues.  The errors pop up and some time afterwards the operation requested completes.  One of two things has to happen to avoid this.  Either Sonos has to execute the function quicker or Sonos has to keep the error messages from jumping the gun.

What did Sonos Support say, when you presented a diagnostic, and called them? I’ve not seen this issue on my system, so I’m working from a theoretical perspective.

I’m also curious as to how you defined that you have no duplicate IP addresses. None of the software/hardware I have show IP addresses over time, but only the moment I run a report, and then only shows devices that are currently connected, and not those that are not. I’d be delighted to know about some solution that can represent that data in a meaningful manner, especially as my current device from T-Mobile doesn’t seem to allow IP reservation/assignments…and I’m semi paranoid. 

 Mine are all reserved and there is only one SSID being broadcasted here.  The Sonos app is showing the errors before the requested operation is completed.  Particularly when I choose to play a large playlist I get an error first then it loads.  Just as a test I chose Play Now for a Qobuz playlist of 965 tracks.  The error Something Went Wrong. Try Again was displayed then right after that the playlist loaded.  It didn’t start playing, but that’s a subject for a different thread.

Then that suggests a deeper issue that might be resolved by a call to Sonos support. Unfortunately, your particular issue isn’t in the ‘most people experience this’ category. 

I’m getting similar errors, albeit with a little smaller playlists. I wish the something went wrong error gave useful information. I know it’s a Sonos app issue as I don’t have the issue when playing the same playlists with SonoPhone. 

 You might be right about most people not experiencing those errors prior to the operation completing.  Maybe, though, they take the error literally and give up before giving time for the request to be completed.  Also could be they find no reason to report this glitch because in the end the request finishes.  Sometimes you just live with these things because it’s not something that stops you from listening.
 

 My goal was to let users, who are understandably impatient with this slow app, know that their request just might work even though the app says it won’t.

With the IP addressing likely eliminated (it is all too common the problem) it is sounding more like a timing or interference issue. A diagnostic and call to Support is the best way to see as the internal data is hidden from us users.

Here I’m just living with the random startup errors and delays, hoping things will stabilize sooner or later.