[web app] when queue reaches 100 songs, songs added start removing songs from bottom of queue

[usernameinvalid]

Plan

Premium

Country

Poland

Device

acer aspire v nitro 

Operating System

Windows 10

My Question or Issue

when the queue reaches 100 songs, songs added start to remove the songs from the bottom of the queue

I made a video showing how it works, but it's too big to attach. 

Basically, to reproduce: 

1) Add at least 100 songs to the queue (just queue several 10+ song albums)

2) Check what song appears last in the queue (usually no. 101) - make sure it's a song in the middle of a queued album

3) Add a new album to the queue

4) Skip a few songs ahead (using the skip button)

5) Check what song appears last in the queue. It will suddenly be the first song of the most recently queued album, even though it should be songs further down on the second-to-last album you queued.

[Jeremy]

Hi there @usernameinvalid,

Thank you for taking the time to post and report this. We checked from our end and was able to replicate the same behavior.

We've reported this to the right team that will investigate this.

In the meantime, can you check if you get the same behavior on the desktop app?

It would also be great if you could let us know your browser version?

If you're able to reproduce on the desktop app, kindly let us know your desktop Spotify version as well.

Once we have the information above we'll mediate the information to the investigation team.

We'll keep an eye out for your reply.

Once again - thank you for reporting this! Take care 🙂 

[usernameinvalid]

Hi Jeremy,

I installed the latest version of the desktop app:

and can confirm the issue does not occur (I have loaded up to 250 songs, I have not checked with more). However, I would like to keep using the web player, as the desktop app has lost the ability to scrobble to last.fm (I have a separate ticket for this).

I am using Edge Version 104.0.1293.70 (Official build) (64-bit). 

[Vasil]

Hey @usernameinvalid,

Thanks for the update!
We managed to replicate this on our end and conveyed the info to the responsible folks 🙂
We'd advise using the app as a workaround for the time being & we're here for you if any further questions arise.
Cheers!