Bug: Backlogged Subsonic scrobbles not sent due to time cutoff #430
Description
Please check existing knowledge before opening an issue
- I have checked the FAQ and documentation
- I have searched through existing issues and discussions.
Describe the Bug
I initially mentioned this in #268 but I think it's different enough from that that it probably should be moved to its own thing.
I've found an issue with backlogged (or in my case, offline) Subsonic scrobbles. With my app of choice (Arepggi) I have to fully reload the app to send the scrobbles through, however if I remember do it too late, they fail to go through as "it occurred ## hours before the oldest scrobble returned by this client":
Platform
Docker
Versions
multi-scrobbler 0.10.7
navidrome 0.59.0
maloja (though this applies to all clients as far as I can tell) 3.2.4
Logs
[2025-12-28 22:53:53.958 -0700] DEBUG : [App] [Scrobblers] [Listenbrainz - ListenBrainz] Will not scrobble The Smashing Pumpkins - This Time @ 2025-12-27T22:52:53-07:00 (S) from Source 'Endpointlz - Navidrome' because it occurred 19 hours before the oldest scrobble returned by this client (2025-12-28T17:42:51-07:00)
[2025-12-28 22:53:53.660 -0700] DEBUG : [App] [Scrobblers] [Lastfm - LastFm] Will not scrobble The Smashing Pumpkins - This Time @ 2025-12-27T22:52:53-07:00 (S) from Source 'Endpointlz - Navidrome' because it occurred 19 hours before the oldest scrobble returned by this client (2025-12-28T17:42:51-07:00)
[2025-12-28 22:53:53.068 -0700] DEBUG : [App] [Scrobblers] [Maloja - Maloja] Will not scrobble The Smashing Pumpkins - This Time @ 2025-12-27T22:52:53-07:00 (S) from Source 'Endpointlz - Navidrome' because it occurred 19 hours before the oldest scrobble returned by this client (2025-12-28T17:42:51-07:00)
[2025-12-28 22:53:52.375 -0700] DEBUG : [App] [Sources] [Endpointlz - Navidrome] Last activity was at 22:53:39-07:00 (00:12 ago) | Next check in 10.00s
[2025-12-28 22:53:49.057 -0700] DEBUG : [App] [Cache] [Scrobble] Saved cache to file
[2025-12-28 22:53:47.796 -0700] INFO : [App] [Sources] [Endpointlz - Navidrome] Discovered => The Smashing Pumpkins - This Time @ 2025-12-27T22:52:53-07:00 (S)Additional Context
I'm not entirely sure what purpose the hour cutoff has (but I presume it's to prevent or mitigate duplicate scrobbles?), but I feel like a setting to change that hour threshold or disable it entirely could be helpful to make sure these backlogged scrobbles actually go through. The tracks appear under Endpointlz's "Tracks Discovered", so they make it to MS, just aren't dished out to the clients.
I'm not sure if I can rely on myself constantly remembering to refresh my app each time I get home lol. I don't see anything in documentation about this, so just want to make sure I'm not missing something small in my config.
Thank you