Re-requests every monday 05:10

[buzdriver]

Description

I've just run the docker two weeks, but both mondays I get a lot of re-requests of series/movies already requested by other users - these requests however come in by different users than the original requester.

Version

48ef298

Steps to Reproduce

Not sure - Process Blacklisted Tags is the only job I can see running with 7 days between.

Screenshots

No response

Logs

Platform

desktop

Database

SQLite (default)

Device

Docker

Operating System

Unraid

Browser

Firefox

Additional Context

No response

Code of Conduct

• I agree to follow Seerr's Code of Conduct

[buzdriver]

2025-12-08T04:10:00.348Z [info][Watchlist Sync]: Creating media request from user's Plex Watchlist {"userId":1,"mediaTitle":"The Witcher"}
2025-12-08T04:10:00.401Z [debug][Watchlist Sync]: Failed to create media request from watchlist {"userId":1,"mediaTitle":"The Witcher","errorMessage":"Auto-request for this media and user already exists."}

2025-12-08T04:10:06.523Z [info][Watchlist Sync]: Creating media request from user's Plex Watchlist {"userId":18,"mediaTitle":"The Witcher"}
2025-12-08T04:10:06.557Z [info][Notifications]: Sending notification(s) for MEDIA_PENDING {"subject":"The Witcher (2019)"}
2025-12-08T04:10:06.559Z [info][Notifications]: Sending notification(s) for MEDIA_AUTO_REQUESTED {"subject":"The Witcher (2019)"}
2025-12-08T04:10:06.559Z [debug][Notifications]: Sending email notification {"recipient":"XXXXXXX","type":"MEDIA_AUTO_REQUESTED","subject":"The Witcher (2019)"}

Not sure - Maybe Jellyseer/seerr creates a request per user even if it's already available? Nothing that happend in Overseerr.
/BR

[fallenbagel]

2025-12-08T04:10:00.348Z [info][Watchlist Sync]: Creating media request from user's Plex Watchlist {"userId":1,"mediaTitle":"The Witcher"}
2025-12-08T04:10:00.401Z [debug][Watchlist Sync]: Failed to create media request from watchlist {"userId":1,"mediaTitle":"The Witcher","errorMessage":"Auto-request for this media and user already exists."}

2025-12-08T04:10:06.523Z [info][Watchlist Sync]: Creating media request from user's Plex Watchlist {"userId":18,"mediaTitle":"The Witcher"}
2025-12-08T04:10:06.557Z [info][Notifications]: Sending notification(s) for MEDIA_PENDING {"subject":"The Witcher (2019)"}
2025-12-08T04:10:06.559Z [info][Notifications]: Sending notification(s) for MEDIA_AUTO_REQUESTED {"subject":"The Witcher (2019)"}
2025-12-08T04:10:06.559Z [debug][Notifications]: Sending email notification {"recipient":"XXXXXXX","type":"MEDIA_AUTO_REQUESTED","subject":"The Witcher (2019)"}

Not sure - Maybe Jellyseer/seerr creates a request per user even if it's already available? Nothing that happend in Overseerr.
/BR

No. Jellyseerr/seerr and overseerr is exactly the same. This might come from the newly changed Plex watchlist api (which is broken on overseerr rn)

[buzdriver]

No. Jellyseerr/seerr and overseerr is exactly the same. This might come from the newly changed Plex watchlist api (which is broken on overseerr rn)

sct/overseerr@362d97d
I'm not sure that would cause this behaviour - it only swapped the API-links? I was running Develop with working watchlist-sync before switching to seerr.
/BR

[fallenbagel]

No. Jellyseerr/seerr and overseerr is exactly the same. This might come from the newly changed Plex watchlist api (which is broken on overseerr rn)

sct/overseerr@362d97d
I'm not sure that would cause this behaviour - it only swapped the API-links? I was running Develop with working watchlist-sync before switching to seerr.
/BR

There was another fix regarding this. But yeah that shouldnt cause any issues either (technically). What you linked is only 1 part of 3 fixes needed.

[fallenbagel]

#1907
#1914

These fixes are related to the api changes which were not added to overseerr as the decision of merger happened at the same time so we decided to PR that to seerr instead.

Nevertheless, except for these fixes, the core code that handles watchlists are exactly the same between overseerr and jellyseerr and seerr. There is no job that runs on that specific timing either.

@buzdriver Could you provide the full logs of when that happens so we can see whats happening as no one else who's using jellyseerr with plex or seerr:develop has reported this issue occurring to them, so we'd need to be able to reproduce this to debug further

[buzdriver]

I'm running AppData Backup, so Plex is offline until 04:10 when Starting scheduled job: Plex Watchlist Sync is run and can connect again. Still don't understand why it would create for those users.
/BR

seerr.log