How to know if edit "worked"?

[larrynator]

I recently joined and made my first edit, adding a release (Keep Believing) for the band Truth. I see it on the musicbrainz site but it has been about 2 days and it hasn’t shown up in lidarr. Even searching in lidarr by the release group id doesn’t find it.

How do I know whether it just needs more time or if I did something wrong and need to correct it? Since this was my first edit I’m betting I left out some piece of information but there are no errors/warnings that I have found.

Thanks!

[outsidecontext]

AFAIK lidarr is running on their own replicated database copy of MusicBrainz. Maybe it gets synced more infrequently, or there is some issue with the sync currently? The lidarr team would know.

[InvisibleMan78]

@larrynator

(Keep Believing) for the band Truth

@larrynator As you can check here, everything is OK on the MB side:

Edits for Keep Believing - MusicBrainz

If Lidarr doesn’t show it:

@larrynator

about 2 days and it hasn’t shown up in lidarr.

there is not much than can be done on MB’s side.

Maybe this is also related to:

For those using Lidarr and MusicBrainz metadata

If you are using Lidarr and experiencing problems with MusicBrainz metadata searches and imports in Lidarr, please read on: [image] This impacts all searches and imports. On 5/21, Musicbrainz pushed a schema change which broke our metadata server. The devs attempted a repair using MB’s scripts, and those failed to work. The devs are currently working on a rebuild of the metadata server, but they are very short on personal time to devote to this, and it will be up when they are able to get to…

I’m not sure if this issue is completely fixed on Lidarr’s side.

If I try to search for the artist name Truth in Lidarr I currently get:

or if I search with the artist MBID 02bc5737-b5b2-43aa-b44b-b9bd676b7307
I only get this currently from Lidarr:

But if I search for an “older” name in Lidarr like Coldplay, I get results, like:

[Weblate]

From AI:
"
Lidarr’s search function was not working due to a broken, third-party MusicBrainz metadata server, which has since been addressed with a rebuilt server and caching mechanism. You can now try to get Lidarr working by switching to a develop version, restarting, and adding api.musicinfo.pro under Metadata > Custom Lidarr if you are on an older version of Lidarr. You may need to hit “Refresh Artists” on your existing library or add new artists to help populate the new cache.

What to Do:

1. Update to the latest version of Lidarr, preferably the develop branch, as these versions have improved metadata server communication.
2. Restart Lidarr after updating.
3. If on a previous version, add api.musicinfo.pro under Metadata > Custom Lidarr.
4. Refresh your library and add new artists to help populate the updated cache.
5. Use the develop version of the Lidarr application, as it includes changes that can help with artist and album lookups.

Why it wasn’t working:

• Metadata Server Failure:Lidarr relies on third-party services like the MusicBrainz metadata server, which failed due to a schema change and a subsequent attempt at a repair that did not work.
• Caching and Server Overload:Because of the failure and the limited time the development team has, the new metadata server is being rebuilt, and the initial search errors you experienced were expected as the cache was populated, according to a Reddit post on August 18, 2025.

Important Considerations:

• Wait for the cache to fill:You may still see some errors as the cache for the new metadata server continues to build.
• New libraries and Spotify lists:New Lidarr libraries or Spotify list additions are not ready and will require waiting for the new server to be fully rebuilt.
• No workaround for the old metadata server:There is no workaround to resolve this issue yourself, and attempting to bypass the metadata server in any way is a violation of the Lidarr community rules.
  "

[Weblate]

At mine:

Searching for new artists failed…“Unable to communicate with LidarrAPI.” : r/Lidarr

And this:

[Weblate]

Positive comments at the end.

Lidarr Update - (The Start of) The Fix : r/Lidarr

[InvisibleMan78]

I just ran a quick test:
Created a new docker container with the mentioned alternative image blampe:lidarr.

This alternative image was created to include a little nginx proxy that redirects the broken (and hardcoded! ) API url to the currently working api.musicinfo.pro URL.

I have not fully tested this container and I have not migrated my existing database!
This was only a test to search for the above “Truth” where I get now a long list of results, including

If you want to proceed with your current data, please be careful and create backups of your database and configuration files!

Just to be clear, this is not an officially supported workaround from the Lidarr team.

Update:
Unfortunately, this alternative Lidarr docker container also DOES NOT SHOW the newly added album:

The two highlighted albums are not available in Lidarr - I have no idea why:

[InvisibleMan78]

With the newest updated lidarr docker container:

Package Version 2.14.5.4836-ls226 by linuxserver.io

I get this 11 Albums, inlcuding “Keep Believing”:

But the album “Praise” is still not listed in lidarr.

In the current lidarr log file, I only found two occurrences of “Praise”:

Unfortunately, I still have no idea why “Praise” does not seem to be found in the metadata, or what that metadata means exactly for lidarr.

Does anyone else have any ideas?

[aerozol]

@InvisibleMan78

But the album “Praise” is still not listed in lidarr.

No format and no tracklist? Seems likely that Lidarr skips it because of one of those issues.