Monitor New Albums :: No longer working [Lidarr v1.2.3.3254] #2988

Author

Owner

@SawkeeReemo commented on GitHub (Jul 3, 2023):

Literally any artist/album. It just stopped working at some point without me changing a thing. And yes, these are new new albums. Not just something added to the database. I’ve since gone through and manually fixed tons of them since I hadn’t heard back, but I’ll keep a look out.

To clarify, these are artists I’ve had in my library for ages (years in some cases). And when the option to monitor new albums came out, I turned that on for tons of them. It always worked as it should; when a new album was released, it would eventually make its way to Lidarr, be monitored, then snagged once it became available. But that stopped a few months ago. Now I will see the artist monitored, the settings are still set to monitor new albums, a new album has been added, but for some reason it’s not monitored and I have to manually click the monitor icon.

I also notice that the ALBUMS heading, for example, turned itself off monitoring as well. And, if you don’t have any albums monitored it will turn itself off as well. Now I pretty much have to have whatever the latest album/EP/single/etc is monitored in order to keep that section monitored.

@SawkeeReemo commented on GitHub (Jul 3, 2023): Literally any artist/album. It just stopped working at some point without me changing a thing. And yes, these are new new albums. Not just something added to the database. I’ve since gone through and manually fixed tons of them since I hadn’t heard back, but I’ll keep a look out. To clarify, these are artists I’ve had in my library for ages (years in some cases). And when the option to monitor new albums came out, I turned that on for tons of them. It always worked as it should; when a new album was released, it would eventually make its way to Lidarr, be monitored, then snagged once it became available. But that stopped a few months ago. Now I will see the artist monitored, the settings are still set to monitor new albums, a new album has been added, but for some reason it’s not monitored and I have to manually click the monitor icon. I also notice that the ALBUMS heading, for example, turned itself off monitoring as well. And, if you don’t have any albums monitored it will turn itself off as well. Now I pretty much have to have whatever the latest album/EP/single/etc is monitored in order to keep that section monitored.

deekerman commented

Author

Owner

@XmnwildX12 commented on GitHub (Jul 24, 2023):

Having the same exact problem for the last 2 months or so, I have a filter I created that looks for the next album in the next 12 weeks and have to go in and manually monitor every single new album for all bands.

@XmnwildX12 commented on GitHub (Jul 24, 2023): Having the same exact problem for the last 2 months or so, I have a filter I created that looks for the next album in the next 12 weeks and have to go in and manually monitor every single new album for all bands.

deekerman commented

Author

Owner

@c-grant commented on GitHub (Jul 24, 2023):

I just found this ticket a it seems I have been having the same issue for a while now. New albums as far back as 2022 are not showing as monitors but the artist is set to monitor all.

Some additional information. At least some of these albums are in the "wanted" menu with the monitored filter option but are shown as not monitored or downloading in the artist. There are thousands of entries in wanted so its hard to vanadate too many

@c-grant commented on GitHub (Jul 24, 2023): I just found this ticket a it seems I have been having the same issue for a while now. New albums as far back as 2022 are not showing as monitors but the artist is set to monitor all. Some additional information. At least some of these albums are in the "wanted" menu with the monitored filter option but are shown as not monitored or downloading in the artist. There are thousands of entries in wanted so its hard to vanadate too many

deekerman commented

Author

Owner

@Whipstickgostop commented on GitHub (Sep 21, 2023):

Same issue here, as far back as 2022. New albums will show up on the artist page as expected, but never get marked monitored.

@Whipstickgostop commented on GitHub (Sep 21, 2023): Same issue here, as far back as 2022. New albums will show up on the artist page as expected, but never get marked monitored.

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 26, 2023):

I'm still back on version 1.5.0.3643, but this is still happening.

@SawkeeReemo commented on GitHub (Oct 26, 2023): I'm still back on version 1.5.0.3643, but this is still happening. ![Screen Shot 2023-10-26 at 3 00 32 PM](https://github.com/Lidarr/Lidarr/assets/60272670/ae06f272-4482-4092-a855-f22814105eca)

deekerman commented

Author

Owner

@Qstick commented on GitHub (Oct 26, 2023):

Do you have that artist set to monitor new items?

@Qstick commented on GitHub (Oct 26, 2023): Do you have that artist set to monitor new items?

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 26, 2023):

Yup. As well as many others. I regularly have to go in and manually click the monitor button if I actually want it to monitor new albums. It’s been this way for about a year now. Can’t remember when I first reported it. Might be longer now…

@SawkeeReemo commented on GitHub (Oct 26, 2023): Yup. As well as many others. I regularly have to go in and manually click the monitor button if I actually want it to monitor new albums. It’s been this way for about a year now. Can’t remember when I first reported it. Might be longer now…

deekerman commented

Author

Owner

@hockeygoalie35 commented on GitHub (Apr 5, 2024):

Also having this issue.

@hockeygoalie35 commented on GitHub (Apr 5, 2024): Also having this issue.

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Apr 8, 2024):

Yup. Still an issue here as well.

@SawkeeReemo commented on GitHub (Apr 8, 2024): Yup. Still an issue here as well.

deekerman commented

Author

Owner

@Mrpink200 commented on GitHub (Jun 27, 2024):

Same for me : https://github.com/Lidarr/Lidarr/issues/4873
Really annoying as we can no longer monitor forthcoming albums
Is it difficult to fix ?

@Mrpink200 commented on GitHub (Jun 27, 2024): Same for me : https://github.com/Lidarr/Lidarr/issues/4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ?

deekerman commented

Author

Owner

@XmnwildX12 commented on GitHub (Jun 27, 2024):

Same for me : #4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ?

While waiting for a fix I have created a custom filter of next album in the next 12 weeks and as they pop up I go in and manually monitor the albums.

@XmnwildX12 commented on GitHub (Jun 27, 2024): > Same for me : #4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ? While waiting for a fix I have created a custom filter of next album in the next 12 weeks and as they pop up I go in and manually monitor the albums.

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Jun 27, 2024):

Any additional comments of "me too" or "Same for me" shall be considered spam and are unhelpful.

You'll likely be waiting awhile as there is only 1 semi-active Servarr (Lidarr/Radarr/Readarr/Prowlarr) dev at this time. Apparently no one from the community believes this is a big enough issue, else there would be a PR to fix it.

If other users wish to be helpful - PR and contribute to fix the issue OR provide recent trace logs and the lidarr version of the issue in addition to ensuring all additional questions that qstick noted

Do you have that artist set to monitor new items?
Some details about the album and artist would be good. The New option only montiors albums that are newer than the newest existing album in the DB. So if an album is added that has a date that is not newer than any other album in DB for that artist, then it should be monitored.

@bakerboy448 commented on GitHub (Jun 27, 2024): Any additional comments of "me too" or "Same for me" shall be considered spam and are unhelpful. You'll likely be waiting awhile as there is only 1 semi-active Servarr (Lidarr/Radarr/Readarr/Prowlarr) dev at this time. Apparently no one from the community believes this is a big enough issue, else there would be a PR to fix it. If other users wish to be helpful - PR and contribute to fix the issue OR provide recent trace logs and the lidarr version of the issue in addition to ensuring all additional questions that qstick noted - Do you have that artist set to monitor new items? - Some details about the album and artist would be good. The New option only montiors albums that are newer than the newest existing album in the DB. So if an album is added that has a date that is not newer than any other album in DB for that artist, then it should be monitored.

deekerman commented

Author

Owner

@Mrpink200 commented on GitHub (Jun 28, 2024):

Do you have that artist set to monitor new items? Some details about the album and artist would be good. The New option only montiors albums that are newer than the newest existing album in the DB. So if an album is added that has a date that is not newer than any other album in DB for that artist, then it should be monitored.

Yes absolutely.
In #4873 that i opened and closed as duplicate i mention an example :
when switching in artist profil monitor new almbums to "new albums", it does not tick the album listed with a release date after today's date;
For example : Nick cave and the bad seeds with album Wild god that has a release date on Aug 30th 2024 cannot be marked as monitored when selecting the option. Same with any other artist that are already prensent in the database and for witch we want to move to "monitored" any release listed in a release date after today
do not hesitate if you are still wondering what happens for us

@Mrpink200 commented on GitHub (Jun 28, 2024): `Do you have that artist set to monitor new items? Some details about the album and artist would be good. The New option only montiors albums that are newer than the newest existing album in the DB. So if an album is added that has a date that is not newer than any other album in DB for that artist, then it should be monitored.` Yes absolutely. In #4873 that i opened and closed as duplicate i mention an example : when switching in artist profil monitor new almbums to "new albums", it does not tick the album listed with a release date after today's date; For example : Nick cave and the bad seeds with album Wild god that has a release date on Aug 30th 2024 cannot be marked as monitored when selecting the option. Same with any other artist that are already prensent in the database and for witch we want to move to "monitored" any release listed in a release date after today do not hesitate if you are still wondering what happens for us

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Jul 1, 2024):

You'll likely be waiting awhile as there is only 1 semi-active Servarr (Lidarr/Radarr/Readarr/Prowlarr) dev at this time. Apparently no one from the community believes this is a big enough issue, else there would be a PR to fix it.

Side question: If we wanted to help out, what skills or coding languages would be most helpful?

@SawkeeReemo commented on GitHub (Jul 1, 2024): > You'll likely be waiting awhile as there is only 1 semi-active Servarr (Lidarr/Radarr/Readarr/Prowlarr) dev at this time. Apparently no one from the community believes this is a big enough issue, else there would be a PR to fix it. Side question: If we wanted to help out, what skills or coding languages would be most helpful?

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Jul 1, 2024):

Do you have that artist set to monitor new items? Some details about the album and artist would be good. The New option only montiors albums that are newer than the newest existing album in the DB. So if an album is added that has a date that is not newer than any other album in DB for that artist, then it should be monitored.

Yes absolutely. In #4873 that i opened and closed as duplicate i mention an example : when switching in artist profil monitor new almbums to "new albums", it does not tick the album listed with a release date after today's date; For example : Nick cave and the bad seeds with album Wild god that has a release date on Aug 30th 2024 cannot be marked as monitored when selecting the option. Same with any other artist that are already prensent in the database and for witch we want to move to "monitored" any release listed in a release date after today do not hesitate if you are still wondering what happens for us

And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library:

@SawkeeReemo commented on GitHub (Jul 1, 2024): > `Do you have that artist set to monitor new items? Some details about the album and artist would be good. The New option only montiors albums that are newer than the newest existing album in the DB. So if an album is added that has a date that is not newer than any other album in DB for that artist, then it should be monitored.` > > Yes absolutely. In #4873 that i opened and closed as duplicate i mention an example : when switching in artist profil monitor new almbums to "new albums", it does not tick the album listed with a release date after today's date; For example : Nick cave and the bad seeds with album Wild god that has a release date on Aug 30th 2024 cannot be marked as monitored when selecting the option. Same with any other artist that are already prensent in the database and for witch we want to move to "monitored" any release listed in a release date after today do not hesitate if you are still wondering what happens for us And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library: ![Screen Shot 2024-07-01 at 1 58 49 PM](https://github.com/Lidarr/Lidarr/assets/60272670/d2c79ccb-17e5-4054-9b2c-7bfb453db71b) ![Screen Shot 2024-07-01 at 1 59 00 PM](https://github.com/Lidarr/Lidarr/assets/60272670/5d9eeaeb-8c53-47d4-b210-3e0ec57a643e)

deekerman commented

Author

Owner

@crafty35a commented on GitHub (Oct 2, 2024):

And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library:

You have it set wrong. Monitor New Albums is set to "No New Albums" which means new albums will not be monitored for that artist.

However, I can confirm that this issue certainly exists even with the proper settings. I have been seeing it for at least two years. I have debug logging enabled and will provide logs as soon as I see this issue again. The Cure's upcoming release (Songs of a Lost World) is not yet showing in Lidarr, and I expect that it will show up soon.

@crafty35a commented on GitHub (Oct 2, 2024): > And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library: You have it set wrong. **Monitor New Albums** is set to "No New Albums" which means new albums will not be monitored for that artist. However, I can confirm that this issue certainly exists even with the proper settings. I have been seeing it for at least two years. I have debug logging enabled and will provide logs as soon as I see this issue again. The Cure's upcoming release (Songs of a Lost World) is not yet showing in Lidarr, and I expect that it will show up soon.

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 5, 2024):

It definitely happened with that new Cure release.

@SawkeeReemo commented on GitHub (Oct 5, 2024): It definitely happened with that new Cure release. ![IMG_9939](https://github.com/user-attachments/assets/7f4ab14b-df63-4de9-a3b3-8458ae9aedcc)

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 11, 2024):

And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library:

You have it set wrong. Monitor New Albums is set to "No New Albums" which means new albums will not be monitored for that artist.

By the way, I do not have it set wrong. This is a bug that’s been around for a while. It started when they implemented the new system where you can only selected “Monitor New Albums” when you first add an artist. All existing artists that were monitoring new albums end up just like I’ve shown here.

@SawkeeReemo commented on GitHub (Oct 11, 2024): > > And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library: > > You have it set wrong. **Monitor New Albums** is set to "No New Albums" which means new albums will not be monitored for that artist. > By the way, I do not have it set wrong. This is a bug that’s been around for a while. It started when they implemented the new system where you can only selected “Monitor New Albums” when you first add an artist. All existing artists that were monitoring new albums end up just like I’ve shown here.

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 11, 2024):

And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library:

You have it set wrong. Monitor New Albums is set to "No New Albums" which means new albums will not be monitored for that artist.

By the way, I do not have it set wrong. This is a bug that’s been around for a while. It started when they implemented the new system where you can only selected “Monitor New Albums” when you first add an artist. All existing artists that were monitoring new albums end up just like I’ve shown here.

Well no need to be rude here. The screenshot that you submitted looks like you have it set wrong. We can understand that when you add an artist the bug is reflected that new albums aren't monitored. I think what we are also saying here is that even when you change the selection to monitor new albums and save, it's not respected, and new albums for an artist are not monitored when the RSS artist sync runs from MusicBrainz

@robant85 commented on GitHub (Oct 11, 2024): > > > And just for some visual aids for whoever may work on this, here's this exact thing happening with an artist in my library: > > > > > > You have it set wrong. **Monitor New Albums** is set to "No New Albums" which means new albums will not be monitored for that artist. > > By the way, I do not have it set wrong. This is a bug that’s been around for a while. It started when they implemented the new system where you can only selected “Monitor New Albums” when you first add an artist. All existing artists that were monitoring new albums end up just like I’ve shown here. Well no need to be rude here. The screenshot that you submitted _looks_ like you have it set wrong. We can understand that when you add an artist the bug is reflected that new albums aren't monitored. I think what we are _also_ saying here is that even when you change the selection to monitor new albums and save, it's not respected, and new albums for an artist are not monitored when the RSS artist sync runs from MusicBrainz

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Oct 11, 2024):

the RSS artist sync runs from MusicBrainz

There is no RSS Artist Sync. This would be the metadata refresh

where you can only selected “Monitor New Albums” when you first add an artist.

Incorrect - you can edit this after artists are added

@bakerboy448 commented on GitHub (Oct 11, 2024): >the RSS artist sync runs from MusicBrainz There is no RSS Artist Sync. This would be the metadata refresh > where you can only selected “Monitor New Albums” when you first add an artist. Incorrect - you can edit this after artists are added ![image](https://github.com/user-attachments/assets/eb0572d6-fb11-4cda-80bb-ed7a51693088)

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 11, 2024):

Well no need to be rude here. The screenshot that you submitted looks like you have it set wrong. We can understand that when you add an artist the bug is reflected that new albums aren't monitored. I think what we are also saying here is that even when you change the selection to monitor new albums and save, it's not respected, and new albums for an artist are not monitored when the RSS artist sync runs from MusicBrainz

First, I realized my original wording may have come off as rude, so I immediately changed it. You must still have seen the original wording in your email or something. Apologies for that, I was trying to be jokey about it but realized it might not come off that way.

Also, yes. This is what I said in my original post about the issue. The recent issue with new releases not being added when the RSS updates is a separate issue which I believe they are aware of. And I THINK you can make a request on their Discord to push through an update if it hasn’t happened. (I’m a little out of the loop right now, but I know that was happening at one point. They had a bot or something set up.)

@SawkeeReemo commented on GitHub (Oct 11, 2024): > Well no need to be rude here. The screenshot that you submitted _looks_ like you have it set wrong. We can understand that when you add an artist the bug is reflected that new albums aren't monitored. I think what we are _also_ saying here is that even when you change the selection to monitor new albums and save, it's not respected, and new albums for an artist are not monitored when the RSS artist sync runs from MusicBrainz First, I realized my original wording may have come off as rude, so I immediately changed it. You must still have seen the original wording in your email or something. Apologies for that, I was trying to be jokey about it but realized it might not come off that way. Also, yes. This is what I said in my original post about the issue. The recent issue with new releases not being added when the RSS updates is a separate issue which I believe they are aware of. And I THINK you can make a request on their Discord to push through an update if it hasn’t happened. (I’m a little out of the loop right now, but I know that was happening at one point. They had a bot or something set up.)

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 11, 2024):

the RSS artist sync runs from MusicBrainz

There is no RSS Artist Sync. This would be the metadata refresh

where you can only selected “Monitor New Albums” when you first add an artist.

Incorrect - you can edit this after artists are added

Yes, but it doesn’t work with artists that were added before this change, as has been evidenced here. It literally just happened with The Cure as I showed you above. And that has always been set to monitor new albums.

@SawkeeReemo commented on GitHub (Oct 11, 2024): > > the RSS artist sync runs from MusicBrainz > > There is no RSS Artist Sync. This would be the metadata refresh > > > where you can only selected “Monitor New Albums” when you first add an artist. > > Incorrect - you can edit this after artists are added > > ![image](https://private-user-images.githubusercontent.com/55419169/375873146-eb0572d6-fb11-4cda-80bb-ed7a51693088.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg2NzY1ODcsIm5iZiI6MTcyODY3NjI4NywicGF0aCI6Ii81NTQxOTE2OS8zNzU4NzMxNDYtZWIwNTcyZDYtZmIxMS00Y2RhLTgwYmItZWQ3YTUxNjkzMDg4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDExVDE5NTEyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiMTVjNDAwNzliOTZkMDdjODJjNzZiMmE4M2VkMTMxMTIyNDc3ZmI1Y2Y0ZGIyOTMyNDY1ZjcwZTQwYzdkMmEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0._JDJbu5e9t7x9CQTtMvP8u_SG2rsFViEW1zdoza2rmQ) Yes, but it doesn’t work with artists that were added before this change, as has been evidenced here. It literally just happened with The Cure as I showed you above. And that has always been set to monitor new albums.

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 11, 2024):

new albums for an artist are not monitored when the RSS artist sync runs from MusicBrainz

Also, I misread you here. So you can ignore my comment about that. (Sorry, exhausted over here. Rough night.)

@SawkeeReemo commented on GitHub (Oct 11, 2024): > new albums for an artist are not monitored when the RSS artist sync runs from MusicBrainz Also, I misread you here. So you can ignore my comment about that. (Sorry, exhausted over here. Rough night.)

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 11, 2024):

the RSS artist sync runs from MusicBrainz

There is no RSS Artist Sync. This would be the metadata refresh

where you can only selected “Monitor New Albums” when you first add an artist.

Incorrect - you can edit this after artists are added

Yes, but it doesn’t work with artists that were added before this change, as has been evidenced here. It literally just happened with The Cure as I showed you above. And that has always been set to monitor new albums.

All good. I think we are all saying the same thing. Apologies on mincing words, not RSS feed, but Metadata refresh.

I'm still having the same problem. Even after changing the option to "Monitor New Albums" when a new album hits MusicBrainz and syncs into Lidarr, it does not monitor it automatically.

@robant85 commented on GitHub (Oct 11, 2024): > > > the RSS artist sync runs from MusicBrainz > > > > There is no RSS Artist Sync. This would be the metadata refresh > > > > > where you can only selected “Monitor New Albums” when you first add an artist. > > > > Incorrect - you can edit this after artists are added > > > > ![image](https://private-user-images.githubusercontent.com/55419169/375873146-eb0572d6-fb11-4cda-80bb-ed7a51693088.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg2NzY1ODcsIm5iZiI6MTcyODY3NjI4NywicGF0aCI6Ii81NTQxOTE2OS8zNzU4NzMxNDYtZWIwNTcyZDYtZmIxMS00Y2RhLTgwYmItZWQ3YTUxNjkzMDg4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDExVDE5NTEyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiMTVjNDAwNzliOTZkMDdjODJjNzZiMmE4M2VkMTMxMTIyNDc3ZmI1Y2Y0ZGIyOTMyNDY1ZjcwZTQwYzdkMmEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0._JDJbu5e9t7x9CQTtMvP8u_SG2rsFViEW1zdoza2rmQ) > > Yes, but it doesn’t work with artists that were added before this change, as has been evidenced here. It literally just happened with The Cure as I showed you above. And that has always been set to monitor new albums. All good. I think we are all saying the same thing. Apologies on mincing words, not RSS feed, but Metadata refresh. I'm still having the same problem. Even after changing the option to "Monitor New Albums" when a new album hits MusicBrainz and syncs into Lidarr, it does not monitor it automatically.

deekerman commented

Author

Owner

@crafty35a commented on GitHub (Oct 11, 2024):

Here are standard, debug, and trace logs showing me syncing The Cure and Lidarr picking up this album for the first time (as expected, it came in unmonitored despite having Monitor New Albums set to "New Albums"
standard.txt
debug.txt
trace.txt

@crafty35a commented on GitHub (Oct 11, 2024): Here are standard, debug, and trace logs showing me syncing The Cure and Lidarr picking up this album for the first time (as expected, it came in unmonitored despite having Monitor New Albums set to "New Albums" [standard.txt](https://github.com/user-attachments/files/17348406/standard.txt) [debug.txt](https://github.com/user-attachments/files/17348405/debug.txt) [trace.txt](https://github.com/user-attachments/files/17348404/trace.txt)

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 15, 2024):

Same for me : #4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ?

While waiting for a fix I have created a custom filter of next album in the next 12 weeks and as they pop up I go in and manually monitor the albums.

Does this still work for you @XmnwildX12 ? I have a filter that resembles yours (by months) but it doesn't show any unmonitored albums, which is obviously what I'm looking for.

@robant85 commented on GitHub (Oct 15, 2024): > > Same for me : #4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ? > > While waiting for a fix I have created a custom filter of next album in the next 12 weeks and as they pop up I go in and manually monitor the albums. Does this still work for you @XmnwildX12 ? I have a filter that resembles yours (by months) but it doesn't show any unmonitored albums, which is obviously what I'm looking for.

deekerman commented

Author

Owner

@XmnwildX12 commented on GitHub (Oct 15, 2024):

Same for me : #4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ?

While waiting for a fix I have created a custom filter of next album in the next 12 weeks and as they pop up I go in and manually monitor the albums.

Does this still work for you @XmnwildX12 ? I have a filter that resembles yours (by months) but it doesn't show any unmonitored albums, which is obviously what I'm looking for.

Looks like this has dried up for me as well, I only have one album in there right now for Jerry Cantrell which was added months ago.

@XmnwildX12 commented on GitHub (Oct 15, 2024): > > > Same for me : #4873 Really annoying as we can no longer monitor forthcoming albums Is it difficult to fix ? > > > > > > While waiting for a fix I have created a custom filter of next album in the next 12 weeks and as they pop up I go in and manually monitor the albums. > > Does this still work for you @XmnwildX12 ? I have a filter that resembles yours (by months) but it doesn't show any unmonitored albums, which is obviously what I'm looking for. Looks like this has dried up for me as well, I only have one album in there right now for Jerry Cantrell which was added months ago.

deekerman commented

Author

Owner

@aevrard commented on GitHub (Oct 27, 2024):

Below a short script in powershell that automatise the monitoring of new album of your collection

`$lidarrApiUrl = "https://LIDARRURL/api/v1" # PUT YOUR LIDARR URL
$ApiKey = $YourAPIKey # PUT YOUR LIDARR API KEY
$albumsUrl = "$lidarrApiUrl/album?apikey=$apiKey"

$response = Invoke-RestMethod -Uri $albumsUrl -Method Get
$NextAlbum = $response | Where-Object {(Get-Date $_.ReleaseDate) -gt (Get-Date).AddDays(-60)}

$UpdateAlbumUrl = "$lidarrApiUrl/album/monitor?apikey=$apiKey"
foreach ($album in $NextAlbum) {
$AlbumPs = [PSCustomObject]@{
albumIds = @($album.id)
monitored = $true
}
$AlbumJson = $AlbumPs | ConvertTo-Json -Depth 2
Invoke-RestMethod -Uri $updateAlbumUrl -Method Put -Body $AlbumJson -ContentType "application/json"
}`

@aevrard commented on GitHub (Oct 27, 2024): Below a short script in powershell that automatise the monitoring of new album of your collection `$lidarrApiUrl = "https://LIDARRURL/api/v1" # PUT YOUR LIDARR URL $ApiKey = $YourAPIKey # PUT YOUR LIDARR API KEY $albumsUrl = "$lidarrApiUrl/album?apikey=$apiKey" $response = Invoke-RestMethod -Uri $albumsUrl -Method Get $NextAlbum = $response | Where-Object {(Get-Date $_.ReleaseDate) -gt (Get-Date).AddDays(-60)} $UpdateAlbumUrl = "$lidarrApiUrl/album/monitor?apikey=$apiKey" foreach ($album in $NextAlbum) { $AlbumPs = [PSCustomObject]@{ albumIds = @($album.id) monitored = $true } $AlbumJson = $AlbumPs | ConvertTo-Json -Depth 2 Invoke-RestMethod -Uri $updateAlbumUrl -Method Put -Body $AlbumJson -ContentType "application/json" }`

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 29, 2024):

That's actually really helpful, I'm trying to convert to bash so that I can run it programmatically on a schedule on my Synology NAS. Any way possible you know of a bash script? I'm getting stuck at the parsing of the JSON response.

@robant85 commented on GitHub (Oct 29, 2024): That's actually really helpful, I'm trying to convert to bash so that I can run it programmatically on a schedule on my Synology NAS. Any way possible you know of a bash script? I'm getting stuck at the parsing of the JSON response.

deekerman commented

Author

Owner

@cohenchris commented on GitHub (Nov 2, 2024):

Got one working in bash. I have LIDARR_URL and LIDARR_API_KEY set in my environment already.

#!/bin/bash

# This script monitors albums if:
# 1. The artist is monitored
# 2. The album has been released in the last 30 days
# 3. The album is not a single
#
# This functionality is built into Lidarr, but has been broken for a while

# Initialize environment
WORKING_DIR=$(dirname "$(realpath "$0")")
source ${WORKING_DIR}/.env

# Define constants
lidarr_api_url="${LIDARR_URL}:8686/api/v1"

# Fetch albums from Lidarr API
albums_url="${lidarr_api_url}/album?apikey=${LIDARR_API_KEY}"
response=$(curl -s -X GET "${albums_url}")

# Calculate the date 30 days ago in the format required
thirty_days_ago=$(date -d "-30 days" +%Y-%m-%dT%H:%M:%SZ)

# Filter albums with a release date within the last 30 days and monitored artists
# If an album has been released in the last 30 days, the artist is monitored, and it's not a single, select it for updating
next_albums=$(echo "${response}" | jq --arg date "${thirty_days_ago}" '.[] | select(.releaseDate > $date and .artist.monitored == true and .albumType != "Single")')

# URL to update album monitoring status
update_album_url="${lidarr_api_url}/album/monitor?apikey=${LIDARR_API_KEY}"

# Loop through each album and update its monitoring status if the artist is monitored
jq -c '{id: .id, artistName: .artist.artistName, title: .title}' <<< "${next_albums}" | while read -r album_json; do
    # Extract the album ID, artist name, and album title
    album_id=$(echo "${album_json}" | jq -r '.id')
    artist_name=$(echo "${album_json}" | jq -r '.artistName')
    album_name=$(echo "${album_json}" | jq -r '.title')

    # Print artist and album name for confirmation
    echo "Monitoring ${album_name} by ${artist_name}..."

    # Prepare JSON data for the monitoring update
    album_update_json=$(jq -n --argjson id "${album_id}" '{albumIds: [$id], monitored: true}')

    # Update monitoring status
    curl -s -o /dev/null -X PUT "${update_album_url}" -H "Content-Type: application/json" -d "${album_update_json}"
done

@cohenchris commented on GitHub (Nov 2, 2024): Got one working in bash. I have LIDARR_URL and LIDARR_API_KEY set in my environment already. ``` #!/bin/bash # This script monitors albums if: # 1. The artist is monitored # 2. The album has been released in the last 30 days # 3. The album is not a single # # This functionality is built into Lidarr, but has been broken for a while # Initialize environment WORKING_DIR=$(dirname "$(realpath "$0")") source ${WORKING_DIR}/.env # Define constants lidarr_api_url="${LIDARR_URL}:8686/api/v1" # Fetch albums from Lidarr API albums_url="${lidarr_api_url}/album?apikey=${LIDARR_API_KEY}" response=$(curl -s -X GET "${albums_url}") # Calculate the date 30 days ago in the format required thirty_days_ago=$(date -d "-30 days" +%Y-%m-%dT%H:%M:%SZ) # Filter albums with a release date within the last 30 days and monitored artists # If an album has been released in the last 30 days, the artist is monitored, and it's not a single, select it for updating next_albums=$(echo "${response}" | jq --arg date "${thirty_days_ago}" '.[] | select(.releaseDate > $date and .artist.monitored == true and .albumType != "Single")') # URL to update album monitoring status update_album_url="${lidarr_api_url}/album/monitor?apikey=${LIDARR_API_KEY}" # Loop through each album and update its monitoring status if the artist is monitored jq -c '{id: .id, artistName: .artist.artistName, title: .title}' <<< "${next_albums}" | while read -r album_json; do # Extract the album ID, artist name, and album title album_id=$(echo "${album_json}" | jq -r '.id') artist_name=$(echo "${album_json}" | jq -r '.artistName') album_name=$(echo "${album_json}" | jq -r '.title') # Print artist and album name for confirmation echo "Monitoring ${album_name} by ${artist_name}..." # Prepare JSON data for the monitoring update album_update_json=$(jq -n --argjson id "${album_id}" '{albumIds: [$id], monitored: true}') # Update monitoring status curl -s -o /dev/null -X PUT "${update_album_url}" -H "Content-Type: application/json" -d "${album_update_json}" done ```

deekerman commented

Author

Owner

@robant85 commented on GitHub (Nov 5, 2024):

Got one working in bash. I have LIDARR_URL and LIDARR_API_KEY set in my environment already.

#!/bin/bash

# This script monitors albums if:
# 1. The artist is monitored
# 2. The album has been released in the last 30 days
# 3. The album is not a single
#
# This functionality is built into Lidarr, but has been broken for a while

# Initialize environment
WORKING_DIR=$(dirname "$(realpath "$0")")
source ${WORKING_DIR}/.env

# Define constants
lidarr_api_url="${LIDARR_URL}:8686/api/v1"

# Fetch albums from Lidarr API
albums_url="${lidarr_api_url}/album?apikey=${LIDARR_API_KEY}"
response=$(curl -s -X GET "${albums_url}")

# Calculate the date 30 days ago in the format required
thirty_days_ago=$(date -d "-30 days" +%Y-%m-%dT%H:%M:%SZ)

# Filter albums with a release date within the last 30 days and monitored artists
# If an album has been released in the last 30 days, the artist is monitored, and it's not a single, select it for updating
next_albums=$(echo "${response}" | jq --arg date "${thirty_days_ago}" '.[] | select(.releaseDate > $date and .artist.monitored == true and .albumType != "Single")')

# URL to update album monitoring status
update_album_url="${lidarr_api_url}/album/monitor?apikey=${LIDARR_API_KEY}"

# Loop through each album and update its monitoring status if the artist is monitored
jq -c '{id: .id, artistName: .artist.artistName, title: .title}' <<< "${next_albums}" | while read -r album_json; do
    # Extract the album ID, artist name, and album title
    album_id=$(echo "${album_json}" | jq -r '.id')
    artist_name=$(echo "${album_json}" | jq -r '.artistName')
    album_name=$(echo "${album_json}" | jq -r '.title')

    # Print artist and album name for confirmation
    echo "Monitoring ${album_name} by ${artist_name}..."

    # Prepare JSON data for the monitoring update
    album_update_json=$(jq -n --argjson id "${album_id}" '{albumIds: [$id], monitored: true}')

    # Update monitoring status
    curl -s -o /dev/null -X PUT "${update_album_url}" -H "Content-Type: application/json" -d "${album_update_json}"
done

FAN-F-IN-TASTIC! Appreciate this so much!

@robant85 commented on GitHub (Nov 5, 2024): > Got one working in bash. I have LIDARR_URL and LIDARR_API_KEY set in my environment already. > > ``` > #!/bin/bash > > # This script monitors albums if: > # 1. The artist is monitored > # 2. The album has been released in the last 30 days > # 3. The album is not a single > # > # This functionality is built into Lidarr, but has been broken for a while > > # Initialize environment > WORKING_DIR=$(dirname "$(realpath "$0")") > source ${WORKING_DIR}/.env > > # Define constants > lidarr_api_url="${LIDARR_URL}:8686/api/v1" > > # Fetch albums from Lidarr API > albums_url="${lidarr_api_url}/album?apikey=${LIDARR_API_KEY}" > response=$(curl -s -X GET "${albums_url}") > > # Calculate the date 30 days ago in the format required > thirty_days_ago=$(date -d "-30 days" +%Y-%m-%dT%H:%M:%SZ) > > # Filter albums with a release date within the last 30 days and monitored artists > # If an album has been released in the last 30 days, the artist is monitored, and it's not a single, select it for updating > next_albums=$(echo "${response}" | jq --arg date "${thirty_days_ago}" '.[] | select(.releaseDate > $date and .artist.monitored == true and .albumType != "Single")') > > # URL to update album monitoring status > update_album_url="${lidarr_api_url}/album/monitor?apikey=${LIDARR_API_KEY}" > > # Loop through each album and update its monitoring status if the artist is monitored > jq -c '{id: .id, artistName: .artist.artistName, title: .title}' <<< "${next_albums}" | while read -r album_json; do > # Extract the album ID, artist name, and album title > album_id=$(echo "${album_json}" | jq -r '.id') > artist_name=$(echo "${album_json}" | jq -r '.artistName') > album_name=$(echo "${album_json}" | jq -r '.title') > > # Print artist and album name for confirmation > echo "Monitoring ${album_name} by ${artist_name}..." > > # Prepare JSON data for the monitoring update > album_update_json=$(jq -n --argjson id "${album_id}" '{albumIds: [$id], monitored: true}') > > # Update monitoring status > curl -s -o /dev/null -X PUT "${update_album_url}" -H "Content-Type: application/json" -d "${album_update_json}" > done > ``` FAN-F-IN-TASTIC! Appreciate this so much!

deekerman commented

Author

Owner

@janaxhell commented on GitHub (May 8, 2025):

Hello, just noticed this issue. What do I put in this part?

# Initialize environment
WORKING_DIR=$(dirname "$(realpath "$0")")
source ${WORKING_DIR}/.env

The lidarr /config path or the /music path?
In my case

/srv/dev-disk-by-uuid-5b67514d-485e-4306-873e-b1cbb54ccf99/Config/lidarr
/srv/dev-disk-by-uuid-BAF04088F0404D37/data/media/music

@janaxhell commented on GitHub (May 8, 2025): Hello, just noticed this issue. What do I put in this part? ``` # Initialize environment WORKING_DIR=$(dirname "$(realpath "$0")") source ${WORKING_DIR}/.env ``` The lidarr /config path or the /music path? In my case ``` /srv/dev-disk-by-uuid-5b67514d-485e-4306-873e-b1cbb54ccf99/Config/lidarr /srv/dev-disk-by-uuid-BAF04088F0404D37/data/media/music ```

deekerman commented

Author

Owner

@robant85 commented on GitHub (May 8, 2025):

Those lines are commented out in my script. I'm not using them at all.

@robant85 commented on GitHub (May 8, 2025): Those lines are commented out in my script. I'm not using them at all.

deekerman commented

Author

Owner

@janaxhell commented on GitHub (May 8, 2025):

Oh, thanks, it works indeed, I thought they were needed.

@janaxhell commented on GitHub (May 8, 2025): Oh, thanks, it works indeed, I thought they were needed.

deekerman commented

Author

Owner

@cohenchris commented on GitHub (May 8, 2025):

Hello, just noticed this issue. What do I put in this part?
# Initialize environment
WORKING_DIR=$(dirname "$(realpath "$0")")
source ${WORKING_DIR}/.env
The lidarr /config path or the /music path? In my case
/srv/dev-disk-by-uuid-5b67514d-485e-4306-873e-b1cbb54ccf99/Config/lidarr
/srv/dev-disk-by-uuid-BAF04088F0404D37/data/media/music

It's used to consume a .env file, which contains LIDARR_URL and LIDARR_API_KEY. So yes, not required, you could also simply set them in the body of the script.

@cohenchris commented on GitHub (May 8, 2025): > Hello, just noticed this issue. What do I put in this part? > > ``` > # Initialize environment > WORKING_DIR=$(dirname "$(realpath "$0")") > source ${WORKING_DIR}/.env > ``` > > The lidarr /config path or the /music path? In my case > > ``` > /srv/dev-disk-by-uuid-5b67514d-485e-4306-873e-b1cbb54ccf99/Config/lidarr > /srv/dev-disk-by-uuid-BAF04088F0404D37/data/media/music > ``` It's used to consume a .env file, which contains LIDARR_URL and LIDARR_API_KEY. So yes, not required, you could also simply set them in the body of the script.

deekerman commented

Author

Owner

@bjaudon commented on GitHub (May 17, 2025):

I made a slight edit to the PowerShell above. It will only update the album if the artist is configured to monitor albums. It will skip over if monitoring is 'none'. For my purposes, I run this once per day so I set the days to only look at the last day, that way if I unmonitor the album manually it will not monitor it again.

$lidarrApiUrl = "http://LIDARRURL/api/v1" # PUT YOUR LIDARR URL
$ApiKey = "APIKEY" # PUT YOUR LIDARR API KEY
$albumsUrl = "$lidarrApiUrl/album?apikey=$apiKey"
$artistsUrl = "$lidarrApiUrl/artist?apikey=$apiKey"

$artistsResponse=Invoke-RestMethod -uri $artistsUrl -method Get
$response = Invoke-RestMethod -Uri $albumsUrl -Method Get
$NextAlbum = $response | Where-Object {(Get-Date $_.ReleaseDate) -gt (Get-Date).AddDays(-1)}

$UpdateAlbumUrl = "$lidarrApiUrl/album/monitor?apikey=$apiKey"

foreach ($album in $NextAlbum) {

    $AlbumPs = [PSCustomObject]@{
        albumIds = @($album.id)
        monitored = $true

    }
 
    $AlbumJson = $AlbumPs | ConvertTo-Json -Depth 2
    $artistMatch = $artistsResponse | Where-Object { $_.id -eq $album.artist.id }
    if ($artistMatch.monitorNewItems -ne "none" ) {
        Invoke-RestMethod -Uri $updateAlbumUrl -Method Put -Body $AlbumJson -ContentType "application/json"
    }

}

@bjaudon commented on GitHub (May 17, 2025): I made a slight edit to the PowerShell above. It will only update the album if the artist is configured to monitor albums. It will skip over if monitoring is 'none'. For my purposes, I run this once per day so I set the days to only look at the last day, that way if I unmonitor the album manually it will not monitor it again. ``` $lidarrApiUrl = "http://LIDARRURL/api/v1" # PUT YOUR LIDARR URL $ApiKey = "APIKEY" # PUT YOUR LIDARR API KEY $albumsUrl = "$lidarrApiUrl/album?apikey=$apiKey" $artistsUrl = "$lidarrApiUrl/artist?apikey=$apiKey" $artistsResponse=Invoke-RestMethod -uri $artistsUrl -method Get $response = Invoke-RestMethod -Uri $albumsUrl -Method Get $NextAlbum = $response | Where-Object {(Get-Date $_.ReleaseDate) -gt (Get-Date).AddDays(-1)} $UpdateAlbumUrl = "$lidarrApiUrl/album/monitor?apikey=$apiKey" foreach ($album in $NextAlbum) { $AlbumPs = [PSCustomObject]@{ albumIds = @($album.id) monitored = $true } $AlbumJson = $AlbumPs | ConvertTo-Json -Depth 2 $artistMatch = $artistsResponse | Where-Object { $_.id -eq $album.artist.id } if ($artistMatch.monitorNewItems -ne "none" ) { Invoke-RestMethod -Uri $updateAlbumUrl -Method Put -Body $AlbumJson -ContentType "application/json" } } ```

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Sep 6, 2025):

https://github.com/Lidarr/Lidarr/pull/5588 being merged later today may fix this, but will certainly allow for better logging to track down this issue

@bakerboy448 commented on GitHub (Sep 6, 2025): https://github.com/Lidarr/Lidarr/pull/5588 being merged later today _may_ fix this, but will certainly allow for better logging to track down this issue

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Sep 12, 2025):

And new logs with v2.14.1.4755 or newer are needed

@bakerboy448 commented on GitHub (Sep 12, 2025): And new logs with [v2.14.1.4755](https://github.com/Lidarr/Lidarr/releases/tag/v2.14.1.4755) or newer are needed

deekerman commented

Author

Owner

@github-actions[bot] commented on GitHub (Sep 12, 2025):

👋 @SawkeeReemo, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide.

@github-actions[bot] commented on GitHub (Sep 12, 2025): :wave: @SawkeeReemo, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our [troubleshooting guide](https://wiki.servarr.com/lidarr/troubleshooting#logging-and-log-files).

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Oct 5, 2025):

still waiting for logs with v2.14.1 or newer

@bakerboy448 commented on GitHub (Oct 5, 2025): still waiting for logs with v2.14.1 or newer

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 20, 2025):

I'm still willing to test. I've just got to wait for an artist I've got monitored to release a new album.

@robant85 commented on GitHub (Oct 20, 2025): I'm still willing to test. I've just got to wait for an artist I've got monitored to release a new album.

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 20, 2025):

This one is going to be a hard one to replicate @bakerboy448. Does anyone still have the hookup with MB that could add an album on an artist just for testing purposes?

@SawkeeReemo do you still have that contact at MusicBrainz?

@robant85 commented on GitHub (Oct 20, 2025): This one is going to be a hard one to replicate @bakerboy448. Does anyone still have the hookup with MB that could add an album on an artist just for testing purposes? @SawkeeReemo do you still have that contact at MusicBrainz?

deekerman commented

Author

Owner

@SawkeeReemo commented on GitHub (Oct 20, 2025):

This one is going to be a hard one to replicate @bakerboy448. Does anyone still have the hookup with MB that could add an album on an artist just for testing purposes?

@SawkeeReemo do you still have that contact at MusicBrainz?

Sorry, that wasn’t me.

As for logs, I can get those soon. I haven’t checked in this particular issue since the resurrection of Lidarr.

Also, for anyone reading, my “fix” for this in the past has been to re-add an artist making sure the Future Albums option is selected. Not a judgement, but a genuine question: Why are we only able to set that when adding a new artist?

@SawkeeReemo commented on GitHub (Oct 20, 2025): > This one is going to be a hard one to replicate [@bakerboy448](https://github.com/bakerboy448). Does anyone still have the hookup with MB that could add an album on an artist just for testing purposes? > > [@SawkeeReemo](https://github.com/SawkeeReemo) do you still have that contact at MusicBrainz? Sorry, that wasn’t me. As for logs, I can get those soon. I haven’t checked in this particular issue since the resurrection of Lidarr. Also, for anyone reading, my “fix” for this in the past has been to re-add an artist making sure the Future Albums option is selected. Not a judgement, but a genuine question: Why are we only able to set that when adding a new artist?

deekerman commented

Author

Owner

@robant85 commented on GitHub (Oct 20, 2025):

This one is going to be a hard one to replicate @bakerboy448. Does anyone still have the hookup with MB that could add an album on an artist just for testing purposes?

@SawkeeReemo do you still have that contact at MusicBrainz?

Sorry, that wasn’t me.

As for logs, I can get those soon. I haven’t checked in this particular issue since the resurrection of Lidarr.

Also, for anyone reading, my “fix” for this in the past has been to re-add an artist making sure the Future Albums option is selected. Not a judgement, but a genuine question: Why are we only able to set that when adding a new artist?

In the very top post created by you, it says:

Steps To Reproduce:

Had a friend add a new album for an artist on Musicbrainz.org

Oh well. Hopefully we can try and reproduce another way.

@robant85 commented on GitHub (Oct 20, 2025): > > This one is going to be a hard one to replicate [@bakerboy448](https://github.com/bakerboy448). Does anyone still have the hookup with MB that could add an album on an artist just for testing purposes? > > > > [@SawkeeReemo](https://github.com/SawkeeReemo) do you still have that contact at MusicBrainz? > > Sorry, that wasn’t me. > > As for logs, I can get those soon. I haven’t checked in this particular issue since the resurrection of Lidarr. > > Also, for anyone reading, my “fix” for this in the past has been to re-add an artist making sure the Future Albums option is selected. Not a judgement, but a genuine question: Why are we only able to set that when adding a new artist? In the very top post created by you, it says: Steps To Reproduce: 1. Had a friend add a new album for an artist on Musicbrainz.org Oh well. Hopefully we can try and reproduce another way.

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Oct 20, 2025):

For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

For editing you can:

Edit Artist for if new items should be monitored
Edit Artist Monitoring for 1x bulk change

@bakerboy448 commented on GitHub (Oct 20, 2025): For support and inquiries, please use our [Discord](http://lidarr.audio/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you. For editing you can: - Edit Artist for if new items should be monitored - Edit Artist Monitoring for 1x bulk change <img width="1194" height="423" alt="Image" src="https://github.com/user-attachments/assets/16088913-e0d6-4fc7-8b34-935552260f9a" /> <img width="1461" height="678" alt="Image" src="https://github.com/user-attachments/assets/1fc0b873-f1e6-45de-8718-43bccd208b7d" />

deekerman commented

Author

Owner

@robant85 commented on GitHub (Nov 6, 2025):

I would love to help with debug logs but it's tricky to capture the problem. We have to know when an artist has a new album coming or has recently been added to MB.

Either that or someone add a "test" album to a monitored artist to see if Lidarr monitors it.

@bakerboy448 do we happen to have any "ins" with any mods over at MusicBrainz that can help us with some temporary entries for our debug logging?

@robant85 commented on GitHub (Nov 6, 2025): I would love to help with debug logs but it's tricky to capture the problem. We have to know when an artist has a new album coming or has recently been added to MB. Either that or someone add a "test" album to a monitored artist to see if Lidarr monitors it. @bakerboy448 do we happen to have any "ins" with any mods over at MusicBrainz that can help us with some temporary entries for our debug logging?

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Nov 6, 2025):

I'm no longer working / contributing on the Servarr Projects and there are no active app developers to my knowledge at this time. The Servarr Infrastructure team is different folks than the app developers.

@bakerboy448 commented on GitHub (Nov 6, 2025): I'm no longer working / contributing on the Servarr Projects and there are no active app developers to my knowledge at this time. The Servarr Infrastructure team is different folks than the app developers.

deekerman commented

Author

Owner

@robant85 commented on GitHub (Nov 6, 2025):

So, wait. What does this mean? This issue in particular isn't going to receive any further attention? Is there someone else we can tag in to this issue? @bakerboy448

@robant85 commented on GitHub (Nov 6, 2025): So, wait. What does this mean? This issue in particular isn't going to receive any further attention? Is there someone else we can tag in to this issue? @bakerboy448

deekerman commented

Author

Owner

@robant85 commented on GitHub (Nov 6, 2025):

Also, sorry to see you go.

@robant85 commented on GitHub (Nov 6, 2025): Also, sorry to see you go.

deekerman commented

Author

Owner

@robant85 commented on GitHub (Jan 24, 2026):

I finally have a debug log from an artist that recently had an album added to MusicBrainz but when Lidarr scanned it, it did not monitor it. The artist is monitored and their profile is set to "Monitor New Albums"

What specific thing am I looking for in the debug that I could post here for review? @Qstick

@robant85 commented on GitHub (Jan 24, 2026): I finally have a debug log from an artist that recently had an album added to MusicBrainz but when Lidarr scanned it, it did not monitor it. The artist is monitored and their profile is set to "Monitor New Albums" What specific thing am I looking for in the debug that I could post here for review? @Qstick

deekerman commented

Author

Owner

@bgrassy commented on GitHub (Feb 3, 2026):

I saw that Mitski had a new single released today, so I took the chance to try to replicate this. I saw the following in debug logs:

2026-02-03 16:51:01.4|Info|RefreshArtistService|Updating Info for Artist 'Mitski' [fa58cf24-0e44-421d-8519-8bf461dcfaa5]
2026-02-03 16:51:01.4|Debug|SkyHookProxy|Getting Artist with LidarrAPI.MetadataID of fa58cf24-0e44-421d-8519-8bf461dcfaa5
2026-02-03 16:51:01.5|Debug|ArtistMetadataRepository|0 artist metadata up to date; Updating 1, Adding 0 artist metadata entries.
2026-02-03 16:51:01.5|Debug|RefreshArtistService|[fa58cf24-0e44-421d-8519-8bf461dcfaa5][Mitski] 0 albums up to date. Adding 2, Updating 28, Merging 0, Deleting 0.
2026-02-03 16:51:01.5|Debug|MonitorNewAlbumService|Album 'My Love Mine All Mine' will not be monitored: Albums without release dates are skipped when existing albums have dates
2026-02-03 16:51:01.5|Debug|MonitorNewAlbumService|Album 'I’ll Change for You' will not be monitored: Albums without release dates are skipped when existing albums have dates

The above error is elevated in MonitorNewAlbumService.cs. It appears that when the artists are fetched from the API (like here: https://api.lidarr.audio/api/v0.4/artist/fa58cf24-0e44-421d-8519-8bf461dcfaa5) the ReleaseDate is always null. The release date is only pulled in later, when we invoke refreshes on the child albums here. It seems like either some modification has to be made to the artist API to get the release date upfront, or another check for updating the monitored status happens after the full album info is refreshed. I'm not sure what the maintainer status is, but I'd be happy to make a PR depending on what strategy is recommended.

@bgrassy commented on GitHub (Feb 3, 2026): I saw that Mitski had a new single released today, so I took the chance to try to replicate this. I saw the following in debug logs: ``` 2026-02-03 16:51:01.4|Info|RefreshArtistService|Updating Info for Artist 'Mitski' [fa58cf24-0e44-421d-8519-8bf461dcfaa5] 2026-02-03 16:51:01.4|Debug|SkyHookProxy|Getting Artist with LidarrAPI.MetadataID of fa58cf24-0e44-421d-8519-8bf461dcfaa5 2026-02-03 16:51:01.5|Debug|ArtistMetadataRepository|0 artist metadata up to date; Updating 1, Adding 0 artist metadata entries. 2026-02-03 16:51:01.5|Debug|RefreshArtistService|[fa58cf24-0e44-421d-8519-8bf461dcfaa5][Mitski] 0 albums up to date. Adding 2, Updating 28, Merging 0, Deleting 0. 2026-02-03 16:51:01.5|Debug|MonitorNewAlbumService|Album 'My Love Mine All Mine' will not be monitored: Albums without release dates are skipped when existing albums have dates 2026-02-03 16:51:01.5|Debug|MonitorNewAlbumService|Album 'I’ll Change for You' will not be monitored: Albums without release dates are skipped when existing albums have dates ``` The above error is elevated in [MonitorNewAlbumService.cs](https://github.com/Lidarr/Lidarr/blob/f6a3e7370540cc25caf3aaf0f1c91e7c085585ac/src/NzbDrone.Core/Music/Services/MonitorNewAlbumService.cs#L51). It appears that when the artists are fetched from the API (like here: https://api.lidarr.audio/api/v0.4/artist/fa58cf24-0e44-421d-8519-8bf461dcfaa5) the `ReleaseDate` is always `null`. The release date is only pulled in later, when we invoke refreshes on the child albums [here](https://github.com/Lidarr/Lidarr/blob/f6a3e7370540cc25caf3aaf0f1c91e7c085585ac/src/NzbDrone.Core/Music/Services/RefreshArtistService.cs#L270). It seems like either some modification has to be made to the artist API to get the release date upfront, or another check for updating the monitored status happens after the full album info is refreshed. I'm not sure what the maintainer status is, but I'd be happy to make a PR depending on what strategy is recommended.

deekerman commented

Author

Owner

@robant85 commented on GitHub (Feb 3, 2026):

That's exactly what I'm seeing in my log too. I think they mentioned earlier that there are no maintainers for Lidarr right now, so the chances of the PR are low. It seems like it could be the fix though.

Have you tried the API call independently of Lidarr and it returned the proper release date in the response?

@robant85 commented on GitHub (Feb 3, 2026): That's exactly what I'm seeing in my log too. I think they mentioned earlier that there are no maintainers for Lidarr right now, so the chances of the PR are low. It seems like it could be the fix though. Have you tried the API call independently of Lidarr and it returned the proper release date in the response?

deekerman commented

Author

Owner

@augustuen commented on GitHub (Feb 4, 2026):

We've pushed a fix for release dates in the artist response. Please try to replicate the issue

@augustuen commented on GitHub (Feb 4, 2026): We've pushed a fix for release dates in the artist response. Please try to replicate the issue

deekerman commented

Author

Owner

@bgrassy commented on GitHub (Feb 4, 2026):

I confirmed that this worked when adding a new album for an artist in my collection! Perhaps the original issue was fixed by https://github.com/Lidarr/Lidarr/pull/5588, but the metadata server update resulted in it resurfacing again. I'm reasonably certain that this is fixed now, but maybe others who have had this issue would like to confirm. Thanks for your help @augustuen!

@bgrassy commented on GitHub (Feb 4, 2026): I confirmed that this worked when adding a new album for an artist in my collection! Perhaps the original issue was fixed by https://github.com/Lidarr/Lidarr/pull/5588, but the metadata server update resulted in it resurfacing again. I'm reasonably certain that this is fixed now, but maybe others who have had this issue would like to confirm. Thanks for your help @augustuen!

deekerman commented

Author

Owner

@robant85 commented on GitHub (Feb 4, 2026):

I'm trying to make sure everything happens organically. It works when I remove and re-add an artist. That's cheating though. I have a few artists with albums coming up that haven't been added to MB yet, I'll keep an eye out for them and report back when they sync into Lidarr.

@robant85 commented on GitHub (Feb 4, 2026): I'm trying to make sure everything happens organically. It works when I remove and re-add an artist. That's cheating though. I have a few artists with albums coming up that haven't been added to MB yet, I'll keep an eye out for them and report back when they sync into Lidarr.

deekerman commented