· The “Date Added” field for both Qobuz and TIDAL albums in Roon is showing the same date.
As far as I know, Qobuz has recently made some changes on their side, and the “Date Added” issue is reportedly being resolved gradually. However, in my case, all Qobuz library albums still show the same “Date Added” value, such as 5 April 2026. Similarly, all TIDAL albums also display the same 5 April 2026 in the “Date Added” field. It seems that the same underlying issue is affecting both Qobuz and TIDAL within Roon. My Roon Server is running on ArchLinux, and I have already tried the following:
Thank you for your patience awaiting a response. We have a few clarifying questions in order to effectively troubleshoot this from here.
Our diagnostics show several Roon Servers associated with your account. Did you recently migrate between machines? When did you move your server to the Early Access track?
If you navigate to Settings → Services for Qobuz or Tidal, what do you see as the last sync?
Lastly, what do you have configured for Background Work? Any custom scheduling? This will be in Settings → Library.
Our diagnostics show several Roon Servers associated with your account. Did you recently migrate between machines?
Really!? I don’t think more than one RoonServers are running at this moment.
When did you move your server to the Early Access track?
I am long term EA user, I can’t remenber when I started,…but
At Feb timeframe, there was “EA RoonServer 2.59 and Roon Bridge 2.60 's mismaching” issue, I escaped, for a while, from EA to Production to play music with 2.6 Bridges. Today, I’m on EA.
If you navigate to Settings → Services for Qobuz or Tidal, what do you see as the last sync?
TIDAL: Last Library Sync
6:10:01
Qobuz: Last Library Sync
6:09:37
Lastly, what do you have configured for Background Work? Any custom scheduling?
Yes, once this new feature was announced on EA, I had set Background audio analysis and Background work analysis to “Scheduled” and “2 am to 6 am”, respectively.
Qobuz is rolling out a fix for a known issue affecting their metadata for import date. This can cause what you’re seeing in Roon for Qobuz content. The fact that Tidal content shows the exact same date, however, suggests that something about these repeated database migrations between Early Access and Production reset the import date to the date of the new sync. Did you restore from a Backup when you migrated between EA and Production, or just download the EA track?
Since streaming content relies on service-provided metadata rather than a fixed local timestamp, these values can shift if Roon reprocesses the library. Unfortunately, once this happens, there isn’t a reliable way to restore the original added dates unless you have a backup from before the change.
If you do have a recent Backup from before the date added that is listed in Roon, try restoring that in the meantime.
Note that, I’m putting new albums, continuously, to play music. So I cannot remember clearly when I restored the backup, before. Might be I did once.
A strange phenomenon is when I put a new Qobuz album, the DateAdded is set such as 14 April. In a sametime, “all” affected Qobuz albums in my library follow to 14 April. Additionally, all DateAdded on TIDAL Albums in my library follows as well. So I cannot find exact date when this strange phenomenon was started.
Might be I restored, the backup. But next, DateAdded are overwritten by new Date when I put a new Qobuz/TIDAL album to my library. Then all DateAdded become same, except local sources.
Today all DateAdded on Qobuz and TIDAL albums in my ROON library are same “14 April 2026”.
We have some great news on this front. Qobuz has officially rolled out a fix on their servers regarding the API metadata issue that was causing these erratic “Date Added” shifts. Since the fix was implemented on their end, it should automatically correct how Roon pulls this data moving forward.
To verify that this fix has completely resolved the behavior for your specific setup, could you please perform a quick test for us?
Add a new Qobuz or TIDAL album to your Roon library today.
Check your older, previously added streaming albums.
Let us know if their “Date Added” fields remain stable, or if they still incorrectly overwrite to today’s date.
I follow the steps. After adding a Qoubuz album, still all ,include the latest added one, Qobuz “Date Added” are same as “20 April 2026”. When I looked into TIDAL side, but all “Date Added” are still “17 April 2026”.
Do I need restart Roon or force to synch to Qobuz/TIDAL, or re-login ?
Here’s some my capture images to follow the steps.
It’s been 6 days … My RoonServer (on ArchLinux) is manual rebooted in every day. Also I have done relogin with Qobuz/TIDAL services. But issues are still there.
Now “Date Added” on all TIDAL and all Qobus alubums are showing 26 April 2026 and 23 April 20206, respectively.
From my feeling, this issue is caused by Qobuz/TIDAL, but maybe by logics on Roon side, such as Date Format missmatching.
I tested Date Add for Qobuz with Copilot in this morning. I added a Qobuz album on my library. And then I run Sync library now on (Settings-Services-Qobuz). Copilot read my log and made the following report;
Title: Qobuz DateAdded Overwritten After Sync — Roon Not Calling Favorites API
Hi,
I’ve run into a serious issue with Qobuz DateAdded values in Roon, and I was able to capture detailed logs during a forced “Sync Library Now” operation.
What happened
Before the sync, all my Qobuz albums showed DateAdded = 23 April 2026
(already incorrect, but consistent)
After clicking Sync Library Now, every Qobuz album changed to 26 April 2026
This includes albums added years ago
What the logs show
During the sync:
Roon never calls any Qobuz favorites API
(favorite/get, user/getFavorites, etc.)
Therefore Roon never receives favorite_date
Roon then treats existing albums as “first-time albums”
Since favorite_date is missing, Roon sets DateAdded to “today”
Why this matters
Roon’s documentation says DateAdded for Qobuz albums should come from Qobuz’s favorite_date.
But since Roon never retrieves it, DateAdded gets overwritten during sync.
What I think is happening
It looks like the Roon Qobuz proxy (qobuz.roonlabs.net) is not returning favorites data, so Roon cannot determine the original DateAdded.
Request
Could the Roon team investigate why favorites API calls are missing, and prevent DateAdded from being overwritten when favorite_date is unavailable?
Hope this helps and I can provide full logs if needed.
Good news in that our team is on the right path towards a fix for this issue.
In the meantime, navigate to Roon Settings > Library > Import Settings and scroll down to “Import date defaults to” and select “File Creation time” (temporarily)
Let me know if this changes the date-added behavior at all. Thank you!
Wow！ It works :-). Now ”Date added” on Qobuz albums are back to original date, and TIDAL albums too. I can say “It’s Solved”. A question, shall I hold the setting to “File creation tme”. Anyway thanks verymatch.
