I’m a volunteer moderator on here, I’ve moved your post over to the Feedback section where Roon management will see it (it’s they that determine procedure and policy).
I took a look at the topic that had been closed … can see it was automatically by the closed by the discourse forum software after a period of inactivity after it was marked as solved (known issue).
From what I understand this was triggered by an unexpected Qobuz change, this did “mess” with the local Roon database. For the vast majority of the affected people waiting 72 hours for the fix to operate did resolve the issue.
For those still with issues … Roon’s support did pin this topic (see below) so it was prominent in the forum). I can see you also post in that topic.
Roon’s support team are monitoring that topic to offer help for those that are still having difficulties.
See …
I’m glad post Qobuz fix, the DB restore worked for you As a mod. we can’t overemphasise the importance of have a good backup strategy in place.
As a mod. we can’t overemphasise the importance of have a good backup strategy in place.