bug:

[y28xml]

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

The play gets detected but seldom updated at the service.

Platform

Docker

Versions

• multi-scrobbler 0.10.0 on docker
• source: plex
• client: listenbrainz

Logs

[2025-09-26 07:56:28.939 +0200] DEBUG  : [App] [Sources] [Plex - unnamed] Last activity was at 07:56:28+02:00 | Next check in 5.00s | No new tracks discovered
[2025-09-26 07:56:26.689 +0200] WARN   : [App] [Scrobblers] [Listenbrainz - unnamed-lz] [Now Playing] Error occurred while trying to update upstream Client, will ignore
Error: Error occurred while trying to update upstream Client, will ignore
    at ListenbrainzScrobbler.processingPlayingNow (CWD/src/backend/scrobblers/AbstractScrobbleClient.ts:977:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
caused by: Error: Error occurred while making Listenbrainz API Playing Now request: 
    at ListenbrainzScrobbler.doPlayingNow (CWD/src/backend/scrobblers/ListenbrainzScrobbler.ts:103:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ListenbrainzScrobbler.processingPlayingNow (CWD/src/backend/scrobblers/AbstractScrobbleClient.ts:973:21)
caused by: AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1122:18)
    at afterConnectMultiple (node:net:1689:7)
[2025-09-26 07:56:23.934 +0200] DEBUG  : [App] [Sources] [Plex - unnamed] Last activity was at 07:56:23+02:00 | Next check in 5.00s | No new tracks discovered

Additional Context

No response

[FoxxMD]

This is a bug specific to updating the "Now Playing" status indicator on Listenbrainz, but not for scrobbling.

ETIMEDOUT

Indicates that this is Listenbrainz not responding to the request from your mutli-scrobbler instance in a reasonable amount of time. Listenbrainz often has slow API service, or unavailable entirely. I encounter it a few times a week.

There's nothing I can really about that, since its the quality of their service, not anything related to MS. Are you still experiencing the problem?