Refresh & Scan not working #3953

New issue

Closed

opened 2026-02-20 03:00:28 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 03:00:28 -05:00

Owner

Originally created by @Conkuist on GitHub (Sep 19, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Hitting the "Scan & Refresh" button for an artist does not add new albums from musicbrainz

deleting the artist and adding it again will add the artist with all albums
so not sure why scan & refresh is not doing the same

Expected Behavior

Hitting the "Scan & Refresh" button for an artist adds all albums that where added to musicbrainz since the last scan

Steps To Reproduce

unable to reproduce error with new install

Environment

- OS: debian 12.7
- Lidarr: 2.6.1.4358
- Docker Install: yes
- Using Reverse Proxy: yes
- Browser: unrelated
- Database: postgres (PostgreSQL) 16.4 (Debian 16.4-1.pgdg120+1)

What branch are you running?

Nightly

Trace Logs?

lidarr_logs.txt

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @Conkuist on GitHub (Sep 19, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior Hitting the "Scan & Refresh" button for an artist does not add new albums from musicbrainz deleting the artist and adding it again will add the artist with all albums so not sure why scan & refresh is not doing the same ### Expected Behavior Hitting the "Scan & Refresh" button for an artist adds all albums that where added to musicbrainz since the last scan ### Steps To Reproduce unable to reproduce error with new install ### Environment ```markdown - OS: debian 12.7 - Lidarr: 2.6.1.4358 - Docker Install: yes - Using Reverse Proxy: yes - Browser: unrelated - Database: postgres (PostgreSQL) 16.4 (Debian 16.4-1.pgdg120+1) ``` ### What branch are you running? Nightly ### Trace Logs? [lidarr_logs.txt](https://github.com/user-attachments/files/17067826/lidarr_logs.txt) ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 03:00:28 -05:00

closed this issue
added the
Type: Support.
label

deekerman commented

2026-02-20 03:00:30 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Sep 20, 2024):

For future reference, please don't post logs directly from docker console because these ones aren't cleansed like the ones the wiki instructs you to provide from.

Closing since it's an invalid bug report due to lack of trace logs, but my advice would've been anyway to hop on our discord to request refreshes by providing MB GUIDs for artists and release groups since the metadata's caching seems to have an attitude at times.

@mynameisbogdan commented on GitHub (Sep 20, 2024): For future reference, please don't post logs directly from docker console because these ones aren't cleansed like the ones the wiki instructs you to provide from. Closing since it's an invalid bug report due to lack of trace logs, but my advice would've been anyway to hop on our discord to request refreshes by providing MB GUIDs for artists and release groups since the metadata's caching seems to have an attitude at times.