For the Samsung Galaxy Note20 family, app permission, channel/category, Focus modes, background restriction, account sync and network should be separated. First, check whether the item exists in the app itself. Check for an active focus mode and any scheduled summary. This is the most common cause and it is invisible from the notification itself.
Differential
Likely causes of “Samsung Galaxy Note20 family notifications are delayed or missing”, and how to tell them apart
- 1
A focus mode or scheduled summary is holding them
What separates it Notifications appear later, in a batch, or not until the phone is unlocked. Focus modes, bedtime schedules and scheduled summaries all do this deliberately and quietly.
How to confirm Check for an active focus mode and any scheduled summary. This is the most common cause and it is invisible from the notification itself.
- 2
Battery optimization is restricting the app
What separates it One app is late while others are prompt, on Android in particular. Aggressive per-app power management stops background work, and notification delivery depends on it.
How to confirm Set that app to unrestricted battery use. This is the single highest-hit-rate action on Android for this symptom.
- 3
Notification permission was never granted or was revoked
What separates it Nothing at all from one app, ever. Both platforms now require explicit permission and it is easy to dismiss the prompt at install time.
How to confirm Check the app's notification permission specifically rather than its in-app settings.
- 4
The app's own settings are off
What separates it The system permission is granted and still nothing arrives. Apps carry their own notification preferences, often per category and per account.
How to confirm Check inside the app as well as in system settings. Both have to agree, and each is capable of silencing the other.
- 5
The event never happened
What separates it Nothing appears in the app's own history either. A notification cannot be missing for something that was never generated.
How to confirm Open the app and look for the item. Present in-app but not notified is a delivery problem; absent in-app is not a notification problem at all.
- 6
Notifications are silent rather than missing
What separates it They are in the shade but made no sound and showed no banner. Delivery style is configurable per app — silent delivery is a real setting.
How to confirm Check the app's alert style for banner, sound and lock-screen settings separately.
- 7
The phone is on a network that blocks push
What separates it Notifications stop on one specific Wi-Fi network and resume on cellular. Restrictive workplace and guest networks block the ports push services use.
How to confirm Compare the same app on Wi-Fi and on cellular data in the same place.
- 8
Signed out of the account, or signed in on another device
What separates it Notifications stopped after signing in elsewhere. Some services deliver to the most recent device only.
How to confirm Check the account status inside the app rather than assuming the session persisted.
- 9
Do Not Disturb during a schedule nobody set deliberately
What separates it Notifications are silent at consistent times of day. Bedtime schedules and driving focus both activate automatically.
How to confirm Look at the focus schedule rather than the notification settings.
Before you touch a setting
Record this first — changing settings destroys the evidence
- Whether the item exists in the app's own history — this splits a delivery problem from an event that never happened, and costs one look.
- Whether it affects one app or all of them.
- Whether notifications are absent, late, or present but silent. Those are three different failures.
- Whether the problem follows a time of day, which points at a schedule rather than a setting.
- Whether it happens on Wi-Fi, on cellular, or both.
- The app's system notification permission, and separately its in-app notification settings.
- The app's battery optimization state.
Try in this order
0 of 9 completedCheck whether the item exists in the app itself
ReversiblePresent in the app but never notified is a delivery problem. Absent from the app entirely is not a notification problem at all, and no notification setting will produce an alert for something that was never generated. One look, and it halves the work.
Check for an active focus mode or scheduled summary
ReversibleFocus modes, bedtime schedules and scheduled summaries hold notifications deliberately and give no indication in the notification itself. This is the most common cause, and a problem that follows a time of day is almost always this.
Separate absent from late from silent
ReversibleAbsent points at permissions or the app. Late points at background restriction or the network. Silent points at the delivery style setting. Three different failures that get reported with the same words.
Set the app to unrestricted battery use
ReversibleAggressive per-app power management stops the background work that notification delivery depends on, and it is applied automatically to apps the phone thinks you use rarely. On Android this is the single highest-hit-rate action for late notifications.
Check the system permission and the in-app settings separately
ReversibleBoth have to agree and each can silence the other independently. An app with system permission granted and its own category switched off delivers nothing, and looking at only one of the two explains nothing.
Compare Wi-Fi against cellular in the same place
ReversibleRestrictive workplace and guest networks block the ports push services use, which stops notifications on that network only. Testing both takes a minute and identifies a cause no phone setting would reveal.
Confirm you are still signed in
ReversibleSome services deliver to the most recent device only, so signing in elsewhere silently stops delivery here. Check the account inside the app rather than assuming the session persisted.
Test with the phone locked
ReversibleNotification behavior differs between an unlocked phone in your hand and a locked one in a pocket, and only the second reflects real use. A fix confirmed with the phone unlocked and awake has tested the easiest case.
Reinstall only after the settings are excluded
Signs you outA reinstall clears the app's own preferences and re-prompts for permission, which is why it sometimes works — but it teaches you nothing about which layer failed, and the same cause will take out the next app.
Model-specific
What is true of this model and not of its siblings
- Model scope
- SM-N986* (Note20 Ultra), SM-N980/SM-N981* (Note20). Current Galaxy family; confirm the complete SM identifier, region and One UI version before repair or firmware instructions.
- Symptom boundary
- This record covers Samsung Galaxy Note20 family when it notifications are delayed or missing. A different symptom on the same hardware, or this symptom on a different Samsung product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
- !Notifications fail across every app after every setting has been checked, which points at the system rather than any app.
- !The service itself is failing to send — the app's own status page or support is the path, not the phone.
- !The phone is on a managed network where push is blocked by policy and only an administrator can change it.
- !Notifications are being relied on for anything safety-critical, which no consumer push service is specified for.
Evidence ledger
Sources behind this answer
Exact questions
Common questions
My notifications arrive hours late.+
On Android this is usually battery optimization restricting the app in the background, and setting that app to unrestricted use is the highest-hit-rate fix. On either platform, check for a scheduled summary or a focus mode — both hold notifications deliberately and neither says so.