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

New Movie request + 4k request = 4k notification too early #770

Closed
ghost opened this issue Jan 28, 2021 · 1 comment
Closed

New Movie request + 4k request = 4k notification too early #770

ghost opened this issue Jan 28, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Jan 28, 2021

Describe the bug
I requested a new movie, not in my library before, for 1080p and 4k.
When the 1080p download finished I received two notifications in Discord.
When the 4k download finished I received no notification.

What version of Overseerr are you running?
develop-3812989a1ce1e07d4af09149008043a6e2e94060

To Reproduce
Steps to reproduce the behavior:

  1. Have a Discord Webhook configured with all possible notification settings, apart from auto-approved messages
  2. Use a user with auto approve movie request setttings, like admin user
  3. Request a new movie and approve it for normal server
  4. Request the same movie for 4k server
  5. Wait for the downloads to finish

Expected behavior
Get one notification when 1080p version finished downloading, get the next notification when 4k version finishes downloading.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Also there is no way in the notification to differentiate between normal and 4k request.

Additional context
After finishing the download for 4k version, it never switched to available. Though to be fair, the 4k plex instance is not connected to Overseerr, only Radarr4k with enabled sync option but I thought that would also be enough to count as available. (started a radarr sync job to be sure it does not switch 4k availability status.)

@github-actions
Copy link

🎉 This issue has been resolved in version 1.18.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

No branches or pull requests

1 participant