Chart inconsistencies showing up on profile.

  • 90
  • Problem
  • Updated 15 hours ago
  • In Progress
  • (Edited)
Hi guys! I seem to be having an issue where some tracks scrobble normally but then register as multiple scrobbles within the website interface causing inaccuracies with Top Artists/Albums/Tracks. Library entries for the tracks themselves seem to be accurate so I presume this is just a glitch in need of correction. None of the tracks shown were played more than once in the past week. Username is tombells86:

.

Kind Regards, -- Tom.

[Updating the title for clarity, as this appears to be a problem with charts showing the wrong values, not duplicate scrobbles per-se. - Jon]
Photo of Tom Bell

Tom Bell

  • 26 Posts
  • 4 Reply Likes

Posted 5 months ago

  • 90
Photo of Jon

Jon, Community & Customer Services

  • 5375 Posts
  • 4045 Reply Likes
Official Response
>>>Seriously guys.  What's up?  My library still hasn't gotten the script run against it.  

I posted an update a few weeks ago, but it looks like my post got buried.  We are no longer running the chart fixup script on individual accounts because it takes 15-45 minutes per user, fails if they're currently scrobbling (or start scrobbling while it's running), and many reports indicate that charts are falling out of sync again almost immediately. 

Instead we're working on a permanent fix for this problem, but this will take longer to complete because we have to re-do how we display charts on the site.  We're sorry for any inconvenience caused by this.

For more details, here's my post from a few weeks ago:

A permanent fix is being worked on, but it looks like it's going to be more involved than I'd hoped -- seems like it's not just a case of finding a bug in the code and fixing it, so much as rebuilding how we do charts to eliminate this problem from happening.  Right now charts are updated separately from scrobbles, and as I understand it, there are situations where those updates can fall out of sync (i.e. be sent twice or more) with your actual scrobble count, particularly for users who scrobble a lot during peak traffic; when there's an outage; or possibly with certain scrobble clients -- there are different ways it can happen, which is why it's happening for some people and not others.  The team are now trying to determine what the most effective solution is -- for instance, an obvious fix would be to build your chart from your actual scrobbles, instead of maintaining charts as a separate database, but then it becomes an issue of performance -- that's why they're trying to figure out at the moment.  

Once again, we'd like to apologise for the inconvenience caused by this issue -- it shouldn't be happening, and I expect it to be fixed as a priority.
(Edited)