Re-check user settings before sending notifications.
See original GitHub issueAfter #19246, we no longer have checks in email/push notification handlers for user settings as we did before. This is important especially for email notifications, which may be sent a long time after the message was sent, and there’s a chance the user modified their notification settings in the meantime.
A PR fixing this issue should share/extract as much code as possible with/from the get_recipient_info function in actions.py
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
How to Not Let App Notifications Ruin Your Life | Clockwise
On Android, open the Settings app. Go to Notifications > App settings. You'll see a list of apps that have recently sent you...
Read more >Manage, view, or delete SharePoint alerts - Microsoft Support
To view and cancel your alerts and change the settings for your alerts, you can use either the User Information page or the...
Read more >Notifications - NodePing
The setting configures how many times NodePing should recheck a service before sending notifications that it is down. The first part of this...
Read more >How to change your notification settings - Front Help Center
Click the gear icon on the top right of Front, go into the Personal settings tab, and select Notifications. Step 2. In your...
Read more >Setting notification preferences in UI16 - ServiceNow Docs
You can set your own notification preferences, including personal subscriptions and channels for receiving them. All users can set these ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I think it makes sense to do this in both code paths, for consistency. Even without the explicit delay we have with email notifications, push notifications can still be delayed up to 10 minutes given the queue garbage-collection code path, so if we think it’s correct to recheck settings, we should do it for both.
A PR for this should also follow-up on 24b1439e9333b25207758178cfa575b96f4c6314, and add checks for bots in the new rechecking system.