Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Plex Recently Added Scan' job doesn't pickup new seasons of a TV show #3276

Closed
1 task done
chrisc96 opened this issue Jan 26, 2023 · 2 comments · Fixed by #3287
Closed
1 task done

'Plex Recently Added Scan' job doesn't pickup new seasons of a TV show #3276

chrisc96 opened this issue Jan 26, 2023 · 2 comments · Fixed by #3287

Comments

@chrisc96
Copy link

Description

What I've noticed is that the Plex recently added job only picks up new media in certain scenarios:

  • It registers movies as available (as it's a single item)
  • It's registers as partially available if a user requests a new show and a single season (single item again)
    BUT
  • If the show already exists and they user has requested an additional season, the media stays as 'requested' and notifications don't get triggered when the Plex Recently Added Scan Runs (every 5 minutes currently).

The status only changes when either the Plex Full Scan or Sonarr full scan runs which is usually many hours afterwards.

I have been running Sonarr V4, but this was happening on older versions of Sonarr (v3) and Overseerr. My TV agent is the Plex one. Unsure if this happens on other agents.

Version

1.32.1

Steps to Reproduce

  1. Request another season of an existing TV show
  2. Wait for it to download and be available in Sonarr/Plex
  3. Run the 'Plex Recently Added Scan' job
  4. See that the status doesn't change from requested
  5. Run the 'Sonnar scan' or 'Plex full scan', and see that immediately the status of the request changes.

Screenshots

No response

Logs

No response

Platform

desktop

Device

All devices

Operating System

Linux (Ubuntu 20.04)

Browser

Chrome

Additional Context

See support ticket where Zehn confirmed this was a bug. More info there: https://discord.com/channels/783137440809746482/1067921459982376970

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
@github-actions
Copy link

🎉 This issue has been resolved in version 1.32.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@chrisc96
Copy link
Author

Just tested and its working now! Legends! Thanks for the quick turnaroud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants