You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst testing Telegram notifications I have noticed that Request Automatically Submitted is not working at all for Telegram. I did not experience this issue with other channels, only Telegram.
Version
v1.33.2
Steps to Reproduce
Go to Settings > Notifications > Select Telegram under Notification Settings
Tick Request Automatically Submitted
Add a show through Plex into Wishlist
Once it is automatically submitted, you will not receive a Telegram notification through the configured bot.
Screenshots
No response
Logs
No response
Platform
smartphone
Device
Galaxy S23 Ultra
Operating System
Android 13
Browser
NA
Additional Context
Other Telegram notifications are working fine.
Email notifications for automatically submitted works fine.
Running Plex Server: Version 1.29.2.6364
Code of Conduct
I agree to follow Overseerr's Code of Conduct
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
👋 @Eisa01, we use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with Overseerr.
Description
Whilst testing Telegram notifications I have noticed that Request Automatically Submitted is not working at all for Telegram. I did not experience this issue with other channels, only Telegram.
Version
v1.33.2
Steps to Reproduce
Screenshots
No response
Logs
No response
Platform
smartphone
Device
Galaxy S23 Ultra
Operating System
Android 13
Browser
NA
Additional Context
Other Telegram notifications are working fine.
Email notifications for automatically submitted works fine.
Running Plex Server: Version 1.29.2.6364
Code of Conduct
The text was updated successfully, but these errors were encountered: