The blue spinning circle has not stopped since April 17th.
I assume Roon is making requests to api.roonlabs.net to identify albums so it seems to be more than a UI nuisance: it’s using local and remote system resources?
Requesting assistance to 1) figure out why the album identification retry queue does not clear and 2) steps I can take to address the issue.
The earliest lines found in the logs are from April 17, 2026 with 4175 albums queued for identification.
04/17 05:01:56 Trace: [identification] retry queue has 4175 albums but none ready for retry yet
On April 30th, I shutdown Roon and used SongKong with the Roon profile enabled to clean up the metadata.
On May 2nd, I started Roon and it logged far fewer albums queued for identification
05/02 05:01:23 Trace: [identification] retry queue has 49 albums but none ready for retry yet
By May 3rd, the retry queue had grown again and continues to grow
05/03 00:15:41 Trace: [identification] retry queue has 1163 albums but none ready for retry yet
This chart shows the album identification queue from April 17 - May 17
The album identification queue has been reduced to 2212 as of May 17, 2026
- The green rectangles can be ignored - they just show the number of times the phrase “[identification] retry queue has NNNN albums but none ready for retry yet” was found
I have taken the following actions to reduce the album identification retry queue.
- Disabled “Background audio analysis” and put off restarting Roon as long as possible
- Bulk-set unidentified albums to “Prefer File” for metadata
- Moved corrupt albums (1 as identified by Roon) out of Roon’s music home folder
- Moved corrupt tracks (6 as identified by ffmpeg) out of Roon’s music folder
- Added a couple folders in Roon’s music folder to “Ignored paths” from Settings → Storage
- Checked for skipped files
- Disabled background work schedule
- Cleaned up 2470 deleted files as identified by Roon
