In my ListenBrainz statistics (I am looking at this month and this year), I am seeing the same track split into multiple entries:

• One entry is correctly linked to the track and the artist

• The other entry is either linked to only the artist or nothing

• Both entries have the same displayed artist/track name

However, when I look at my listen history, all listens for this track are correctly linked. I use the same Navidrome setup with Feishin for almost all of the scrobbles, except for rare cases when I use Amperfy. I have configured Navidrome to scrobble and have linked my Spotify account in Listenbrainz as well. However, the majority of my scrobbles come from Navidrome. I am using beets to manage my library. All of the scrobbles for the problematic track should have the same metadata. I have this issue happening for multiple tracks.

I will show the most recent track with this issue ("I love you, love you too") as an example. In Feishin with my Navidrome server, it shows that I have played the song 66 times, but in the ListenBrainz stats for this month, it shows 31 for one entry and 33 for the other. Counting the entries in the listen history, it also seems to appear around 70 times, all hyperlinked. It doesn't appear in the mass listens tool. You can see the issue occur with 3 different tracks in this screenshot.

I've waited to see if it would fix itself over time, but there are tracks that are still split after a few months. I have a hypothesis as to why the issue occurs. I have only seen this issue occur on newly released tracks. Usually, I am the one who adds the entry into MusicBrainz right when it releases, and then I start scrobbling right after, and for a brief period, the entries show as unlinked, so I am thinking that may be related. All of the scrobbles show as linked now in the listen history, but I am suspecting that maybe the stats aggregation captured the listens before MBID resolution completed, and those listens remain as an unlinked entry in stats. I'm not very familiar with the internals of ListenBrainz, so I may be misunderstanding how stats aggregation is supposed to work, but this seems like a mismatch between the listen data and the stats view.