Push Troubleshooting

Every reason a Drumbeats browser push alert might not arrive — permissions, Do Not Disturb, lost subscriptions, service workers — and how to fix each.

Browser push notifications require permission at two layers — the browser and the operating system — and they fail silently when Do Not Disturb is on or the service worker is unregistered. This page walks every reason a Drumbeats push alert might not arrive and the fix for each.

If push worked once and stopped, jump to Step 4 — Lost subscriptions. If you never received the test notification on first setup, work through the steps in order.

Step 1 — Browser permission

  1. Open Drumbeats in the browser where you enabled push.
  2. Click the lock icon (or site-settings icon) in the address bar.
  3. Find Notifications in the site permissions list.
  4. Confirm it is set to Allow (not Block, not Ask).

If it shows Block, reset to Allow using the browser-specific steps below.

Chrome / Edge

  1. Open chrome://settings/content/notifications (or edge://settings/content/notifications for Edge).
  2. Under Not allowed, find drumbeats.io.
  3. Click the three-dot menu next to it → Allow.
  4. Reload Drumbeats and re-enable push from Notifications → Channels.

Firefox

  1. Open about:preferences#privacy.
  2. Scroll to Permissions → Notifications → Settings.
  3. Find drumbeats.io; set status to Allow.
  4. Reload and re-enable push.

Safari (macOS)

  1. Open Safari → Settings → Websites → Notifications.
  2. Find drumbeats.io; set to Allow.
  3. Reload and re-enable push.

Step 2 — Operating system permission

Even when the browser permission is correct, the OS can block all notifications from that browser. This is the single most common cause of "push set up but nothing arrives".

macOS

  1. Open System Settings → Notifications.
  2. Find your browser (Chrome, Firefox, Safari, Edge) in the app list.
  3. Confirm Allow Notifications is ON.
  4. Return to Drumbeats and click Send Test on the push channel.

Windows

  1. Open Settings → System → Notifications.
  2. Confirm Notifications is ON at the top.
  3. Scroll down to the app list and confirm your browser is ON.

iOS (Safari, iOS 16.4+)

Push requires Drumbeats to be installed to the Home Screen first:

  1. Open Drumbeats in Safari.
  2. Tap the Share button → Add to Home Screen.
  3. Open Drumbeats from the new Home Screen icon.
  4. Open Notifications → Channels and enable push.
  5. If push still does not arrive: open Settings → Notifications → Safari (or the web app name) → Allow Notifications ON.

Android (Chrome)

  1. Open Settings → Apps & notifications → Chrome → Notifications; confirm enabled.
  2. In Chrome, open Site settings → Notifications; confirm drumbeats.io is in the Allowed list.

Linux

Desktop notification handling varies by distribution. Check your system notification settings (for example GNOME Settings → Notifications) and confirm your browser is allowed to show notifications.

Step 3 — Do Not Disturb and Focus modes

Do Not Disturb / Focus mode suppresses every notification, including Drumbeats push.

  • macOS — check the Focus indicator in the menu bar. A moon icon means Focus is on.
  • Windows — check Focus Assist in the notification area (bottom-right).
  • iOS / Android — check the DND toggle in Control Center / Quick Settings.

For genuinely critical monitors, add a backup channel that does not depend on browser push — Telegram, Email, or a Webhook into PagerDuty all bypass OS-level DND.

Step 4 — Lost subscriptions

The push subscription lives in the browser. Clearing site data (cookies, cache, "Clear browsing data") deletes it, and Drumbeats has no way to reach your browser until you re-subscribe.

Symptoms:

  • Push channel exists in Drumbeats but no alerts arrive.
  • The Channels page shows a warning that the subscription is missing.

Fix:

  1. Open Notifications → Channels.
  2. Delete the existing push channel.
  3. Click Enable on This Device to create a new subscription.
  4. Verify with Send Test.

Step 5 — Service-worker issues

Browser push depends on Drumbeats's service worker being registered and active. If the service worker is broken, push silently fails.

To check (Chrome / Edge):

  1. Open DevTools → Application → Service Workers.
  2. Confirm a service worker for drumbeats.io is listed as activated and running.

If missing or erroring:

  1. Application → Storage → Clear site data.
  2. Reload the page.
  3. Re-enable push from Notifications → Channels.

Diagnostic flow

plaintext
1. Did the setup test notification arrive?
   No  → Step 2 (OS settings) is the usual cause.
   Yes → Push works. Skip to step 3 below.

2. Did push work before and stop?
   Yes → Step 4 (lost subscription) — re-enable.
   No  → Step 1 then Step 2.

3. Test arrives but real alerts don't?
   → The push channel is not on the notification group attached to the firing monitor.
     Check Notifications → Groups and the monitor's Notification Group setting.

4. Still stuck?
   → Email support@drumbeats.io with your OS, browser version, and the warning
     shown on the Notifications page (if any).
1. Did the setup test notification arrive?
   No  → Step 2 (OS settings) is the usual cause.
   Yes → Push works. Skip to step 3 below.

2. Did push work before and stop?
   Yes → Step 4 (lost subscription) — re-enable.
   No  → Step 1 then Step 2.

3. Test arrives but real alerts don't?
   → The push channel is not on the notification group attached to the firing monitor.
     Check Notifications → Groups and the monitor's Notification Group setting.

4. Still stuck?
   → Email support@drumbeats.io with your OS, browser version, and the warning
     shown on the Notifications page (if any).