[GH-ISSUE #10] Errant disappearing user #9

Closed
opened 2026-02-27 20:07:39 +03:00 by kerem · 2 comments
Owner

Originally created by @tomballgithub on GitHub (Jun 22, 2025).
Original GitHub issue: https://github.com/misiektoja/spotify_monitor/issues/10

I'm using a Spotify account that I don't care about to monitor myself. I received emails this morning and then saw this in the log. This should be filtered out, presumably due to an incorrect response from Spotify

Timestamp:			Sun, 22 Jun 2025, 08:42:01
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Spotify user '[redacted]' ([redacted]) has disappeared - make sure your friend is followed and has activity sharing enabled. Retrying in 3 minutes
Sending email notification to [redacted]
Timestamp:			Sun, 22 Jun 2025, 09:06:46
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Spotify user [redacted] ([redacted]) has reappeared!
Sending email notification to [redacted]
Timestamp:			Sun, 22 Jun 2025, 09:09:49
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
❌ Error: Request timed out while trying to fetch config JSON. Timeout values: [connect: 10s, read: 30s]
Originally created by @tomballgithub on GitHub (Jun 22, 2025). Original GitHub issue: https://github.com/misiektoja/spotify_monitor/issues/10 I'm using a Spotify account that I don't care about to monitor myself. I received emails this morning and then saw this in the log. This should be filtered out, presumably due to an incorrect response from Spotify ``` Timestamp: Sun, 22 Jun 2025, 08:42:01 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────── Spotify user '[redacted]' ([redacted]) has disappeared - make sure your friend is followed and has activity sharing enabled. Retrying in 3 minutes Sending email notification to [redacted] Timestamp: Sun, 22 Jun 2025, 09:06:46 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────── Spotify user [redacted] ([redacted]) has reappeared! Sending email notification to [redacted] Timestamp: Sun, 22 Jun 2025, 09:09:49 ───────────────────────────────────────────────────────────────────────────────────────────────────────────────── ❌ Error: Request timed out while trying to fetch config JSON. Timeout values: [connect: 10s, read: 30s] ```
kerem closed this issue 2026-02-27 20:07:39 +03:00
Author
Owner

@tomballgithub commented on GitHub (Jun 23, 2025):

I saw this again at 6am with the latest code base

<!-- gh-comment-id:2996891022 --> @tomballgithub commented on GitHub (Jun 23, 2025): I saw this again at 6am with the latest code base
Author
Owner

@misiektoja commented on GitHub (Jun 24, 2025):

Hey,

Yes, it is issue with the Spotify endpoint and it's been bugging me since I developed the tool. Funny enough, it also affects the official Spotify client - sometimes the friend activity feed stalls and the friend disappears from the list. It's the same glitchy API issue as seen with the tool.

Fortunately it does not happen too often. It might need a fix similar to what I did for some API glitches in the spotify_profile_monitor. The tricky part is that the response is the same when you've unfollowed the monitored user or the user stops sharing their listening activity - something you'd probably want to catch ... and since it can sometimes happen for more than an hour, there's virtually no way to tell if it's a glitch or intentional action by the user.

I need to ponder over whether there's a clever way to tackle this. I'll dive into it when I find some time.

<!-- gh-comment-id:3000774646 --> @misiektoja commented on GitHub (Jun 24, 2025): Hey, Yes, it is issue with the Spotify endpoint and it's been bugging me since I developed the tool. Funny enough, it also affects the official Spotify client - sometimes the friend activity feed stalls and the friend disappears from the list. It's the same glitchy API issue as seen with the tool. Fortunately it does not happen too often. It might need a fix similar to what I did for some API glitches in the spotify_profile_monitor. The tricky part is that the response is the same when you've unfollowed the monitored user or the user stops sharing their listening activity - something you'd probably want to catch ... and since it can sometimes happen for more than an hour, there's virtually no way to tell if it's a glitch or intentional action by the user. I need to ponder over whether there's a clever way to tackle this. I'll dive into it when I find some time.
Sign in to join this conversation.
No labels
Stale
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify_monitor#9
No description provided.