I just installed the latest production release and the Artist that was stuck in my Listen Later is now gone. So they must have fixed something. 
Hello @DrTone ,
It sounds like the latest release did in fact help with your issue, I’m glad to have been proven wrong 
. I’ll go ahead and mark the thread for closure, thanks for confirming the changes helped!
I had my ghost artist reappear right after I added a local copy of an album of which I had marked for Listen Later on Qobuz. In all honesty I believe this the first time I’ve done this scenario after it disappeared post update mentioned above. The ghost artist didn’t actually appear right after I added this local copy of the album but after a server reboot. I’ve added many albums since I thought this issue was resolved and rebooted the server many times. So I believe it’s somehow related to the above mentioned scenario.
I played around with marking the album as listen later and adding the online version as well with multiple reboots and still the unrelated ghost artist persisted.
When I clicked on listen for this ghost entry, that artist then showed up twice in my list, once with listen later on and a second time with listen later off. When I then turned listen later off on the second appearance the first appearance still stayed in my Listen Later queue.
On a whim, I restarted my server. At that point the ghost artist disappeared again and is no longer in my list.
Hi @DrTone,
Thank you for your post. We’ll ensure this ticket remains active while the team investigates this report.
For context, have you recently performed any of the following database actions?
- Restored a Backup?
- Migrated Roon between machines?
- Added or deleted any Watched Folders?
- Added or removed a streaming service?
We’ll watch for your response. Thank you!
Thanks @DrTone. We’ve captured the event in logs and will reach out here once we have more progress on this issue.
Hey @DrTone,
Our QA team attempted to reproduce this multiple times, but came up empty-handed each time, unfortunately. Without being able to replicate this in-house, it’s difficult to better understand what might be the underlying cause, although I do think you’re onto something with the above scenario you’ve mentioned.
We’ll close this thread for now since a reboot managed to resolve the issue again, but certainly ping us if you experience this another time. 