Prevent suspension of auto-requesting media from plex watchlist (do not allow plex oath token to expire if website unused?)

[zwimer]

Description

Currently, users (with permission) can enable auto-requesting media found in their plex watchlist. However, if the user stops using Jellyseerr directly (i.e. using the website), this watchlist monitoring seems to stop working after a few weeks; once the user logs back into Jellyseerr, the auto-requesting of their watchlist resumes.

What I suspect is happening is:

1. User enables auto request
2. User doesn't interact directly with Jellyseerr so the plex oath login expires
3. Since the oath login is expired, Jellyseerr cannot use it to sync the plex watchlist, hence auto-requesting the watchlist is suspended
4. When the user logs back in via plex oath, Jellyseerr can once more read the watchlist, so auto-requests resume

This issue is preventing about point 3.

Desired Behavior

Jellyseerr does not ever suspend auto-requesting from the plex watchlist. Which I suspect means keeping the oath login valid even if the user doesn't directly interact with the website.

Additional Context

Some users might only use the plex app on their TV, so they frequently don't login to the Jellyseerr website directly for extended periods of time. Since there is no form of notification that this auto-requesting has been suspended (presumably due to the oath expiring), they never know they need to fix it.

I suspect this suspension of auto-requests is not intended behavior, technically a bug, but rather just a consequence of how Jellyseerr handles plex oath timeouts. Tautulli, for example, is an app that does not need such frequent logins to stay connected to plex, so I imagine this is possible with Jellyseerr. I'm not sure if it'd involve extending login timeouts or something else behind the scenes

Code of Conduct

• I agree to follow Seerr's Code of Conduct

[zwimer]

@fallenbagel The issue you linked, if solved, would also solve this, but I don't think it's a duplicate. If the plex API doesn't allow the other issue to be resolved anytime soon, this issue is independently solve-able.

[0xSysR3ll]

Reopened this issue. The Refresh Token job is part of the watchlist auto-request issue and should keep the user's token active, but currently it doesn't do anything.