Qobuz favorites erased in Roon despite being faved in Qobuz (ref#JWO22Q)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon just erased my Qobuz favorites, but they're still faved in Qobuz. I watched it happen in real time - my album count went down by almost 5000 albums as I watched. All of those albums are still marked as faved in the Qobuz app, but no longer in Roon. The Roon log contains line after line like this:
05/05 11:04:36 Debug: [music/storage] processing simple delete for 202:0:60685998 from Qobuz Storage Library
05/05 11:04:36 Debug: [music/storage] LibraryTrack[22435634, Matthias Goerne, Leif Ove Andsnes - Schumann: Liederkreis Op. 24 & Kernerlieder, Op. 35 - Liederkreis, Op. 24: 1. Morgens steh' ich auf IsAvailable=True IsDeleted=False ]

Tell us about your home network

· Unifi UDM Pro, hardwired to ethernet. No VPN

I’ve re-booted Roon Server on my Sonictransporter i5, and signed out of Qobuz and signed back in. Neither has had any effect.

Obviously have not done this clean up. Can it be reversed??

I’ve restored to yesterday’s backup, which has resolved the Qobuz mismatches. But that’s darn weird behavior in Roon, and it took me over two hours to fix. Since this issue has come up periodically in this forum over the years, perhaps my logs are helpful data?

Hi @Daniel_Gercke,

Thanks for sending the logs and for restoring to yesterday’s backup. It’s good to hear that resolved the Qobuz mismatches, even if the behavior in Roon was a painful one to work through.

Was this happening after today’s latest update? And has the system stayed stable since you performed the restore?

Hi Noris! Yes, this occurred just after the update, and so far it has been stable since the reversion/library cleanup/cache emptying.

As mentioned, this issue rears its ugly head periodically (and seems kind of random about which users are affected). Unfortunately, attempts by the user to fix this are usually temporary at best. Given a little time, and without action by the user, the issue usually resolves itself (either at Qobuz’s end or Roon’s end?).

I don’t remember ever seeing an explanation from Roon about why this happens.