Meeting reminder guide
Browser Meeting Notification Troubleshooting
Notification failures usually occur at one of several layers: account session, app state, browser permission, operating-system permission, or device power state.
Test the application state
Confirm you are signed in, the meeting appears in the dashboard, its time and time zone are correct, and a Meeting Guardian tab remains open. Create a manual event a few minutes ahead to isolate calendar sync from alarm behavior.
Check browser and operating-system permission
Open the site's browser permission panel and allow notifications. Then check the operating system's per-browser notification settings, Focus or Do Not Disturb mode, sound output, and banner style.
In-app alarms and optional system notifications are related but not identical. The visible in-app alarm requires the tab to be running; a denied browser permission can prevent the separate system notification.
Check sleep, tabs, and sessions
A sleeping laptop, closed browser, discarded tab, expired session, or different browser profile can interrupt delivery. Keep the device awake during the test and use the same browser profile you use for work.
Sources and further reading
Questions
- Does Meeting Guardian work with its tab closed?
- No. Keep the tab open for alarms to fire.
- Why does the meeting appear but no system notification shows?
- Browser or operating-system notification permission may be denied even though the in-app schedule is correct.
Turn the checklist into an alarm workflow
Add a manual test meeting or connect Google Calendar or Outlook with read-only access.
Create free account