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

[Issue]: Webhook sometimes sends info about new media twice #181

Open
1 task done
ClaraCrazy opened this issue Jun 25, 2023 · 2 comments
Open
1 task done

[Issue]: Webhook sometimes sends info about new media twice #181

ClaraCrazy opened this issue Jun 25, 2023 · 2 comments
Labels
bug This PR or Issue describes or fixes something that isn't working

Comments

@ClaraCrazy
Copy link

ClaraCrazy commented Jun 25, 2023

Please describe your bug

Using discord webhook exclusively for sending available content. I noticed that sometimes the last media, or the last batch of media that has been added, suddenly gets sent via webhook a second time.

I did some digging and by now am able to somewhat reliably reproduce it. For this, its important to know that I have a setup with a download manager. It seems that whenever a new media is added to it, the folder is created and the download begins, this folder creation, or maybe its also just once the nfo file is downloaded (not sure) triggers a scan, (because I configured it that way). Why this re-sends already sent notifications is what im absolutely unsure about. Once the media is actually fully available on the server, and itself sends a notification over webhook, that works just fine. But next time something new is downloading, that last media item is being sent once more again.

I realize this might be confusing, so here in simple words:

  • Movie A is downloaded. Movie A sends webhook notification
  • Movie B, C and D start to download. Movie A sends a second Webhook notification
  • Movie B, C and D are done downloading. They now send their webhook notification
  • Movie E is starting to download. Movie B, C and D send a second webhook notification

If theres any logs that would be useful for this, or anything I can try, please let me know. I'm a developer myself and well versed with the command line etc. so hit me with it :)

Jellyfin Version

10.8.10

if other:

No response

Environment

- OS: Debian 12
- Linux Kernel: 6.1.0-9-amd64
- Virtualization: None
- Clients: *Not applicable for issue*
- Browser: *Not applicable for issue*
- FFmpeg Version: *Not applicable for issue*
- Playback Method: *Not applicable for issue*
- Hardware Acceleration: *Not applicable for issue*
- GPU Model: *Not applicable for issue*
- Plugins: Too many to list. see screenshot
- Reverse Proxy: Apache2
- Base URL: /
- Networking: Host
- Storage: local

Jellyfin logs

Unfortunately the logs dont give anything useful. its all just generic

[2023-06-25 00:12:45.060 +02:00] [INF] Queuing task "ItemAddedScheduledTask"
[2023-06-25 00:12:45.060 +02:00] [INF] Executing "Webhook Item Added Notifier"
[2023-06-25 00:12:45.060 +02:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds

FFmpeg logs

/

Please attach any browser or client logs here

/

Please attach any screenshots here

image

Code of Conduct

  • I agree to follow this project's Code of Conduct
@ClaraCrazy ClaraCrazy added the bug This PR or Issue describes or fixes something that isn't working label Jun 25, 2023
@crobibero crobibero transferred this issue from jellyfin/jellyfin Jun 25, 2023
@ClaraCrazy
Copy link
Author

thanks for transfering, was unware of this repo. Also updated my comment with a foolproof example of what im talking about, since explaining isnt my strength

@lluisd
Copy link

lluisd commented Dec 15, 2024

I have the same issue exactly as you said with logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This PR or Issue describes or fixes something that isn't working
Projects
None yet
Development

No branches or pull requests

2 participants