The pagination to view older Listens is broken on my profile (of the same name), something I've only recently noticed. For example, on my "Listens" tab, if I click on the "Older" button, the page will load, but the Listens that should be there from last night, are not. Instead, Listens from three weeks ago are shown. Now, if I reload the page, the URL doesn't change (the ?max_ts value remains the same), but the reloaded page now correctly displays last night's Listens. Doing this however breaks the "Older" and "Newer" buttons, as a click of either doesn't navigate anywhere any longer (or if a navigation succeeds, the button will become greyed-out and deactivated, i.e. unclickable, after that, even though the first or last page hasn't yet been reached).

Maybe someone could initiate a refresh of my stats? That could possibly bring things back into alignment for me.

I believe my issue may be related to issue LB-809. I have also experienced what it speaks of after manually deleting listens, but after waiting a few days, the reports/charts have always caught up to the state of the "Listens" tab. I thought updates were simply slow, but apparently it's a bug. I feel like my manual deletions are the reason behind my "Listens" pages being broken.

For whatever reason, I've tried to never submit a Listen for a recording that I've already submitted one for (see my all time top recordings, they should all read 1), though I've mistakenly submitted some multiple times, and so I've deleted those. Because of the issue I'm now reporting, it was impossible to find and delete one of these Listens in particular because it simply wasn't being shown on any page, that was, until I realised I must reload the page after each navigation to show the true Listens for a page. Now that I've just deleted it, the report and chart stats should eventually update to reflect this (at least, that has always been the case for me).

There are also other peculiarities with stats shown on my profile (such as the same all time top artists/releases appearing more than once), but I'm not sure if they are of my doing (wrong/missing MBIDs on submission?) or just a bug that a refresh would amend, so I'll wait on opening any further issues.

Thanks.