Not Receiving Notifications

Missing a due-date reminder or an @mention can derail a whole handoff. Notification failures almost always come down to one of four layers: your Loomstack notification settings, a muted project, the delivery channel itself (email, push, or Slack), or device-level permissions. Work through the layers in that order.

Check What Loomstack Is Actually Sending

Before debugging delivery, confirm the notification was generated at all:

1. Click the bell icon in the top bar — this in-app feed shows every notification Loomstack created for you, regardless of channel
2. If the event you expected is missing from the feed, the problem is your settings, not delivery:
   • Go to Settings > Notifications and check that the event type (mentions, assignments, due dates, status changes) is enabled
   • Open the project in question, click the three dots > Notification level — a project set to Muted suppresses everything except direct @mentions
3. If the event is in the feed but never reached your email/phone/Slack, continue to the relevant section below

Email Notifications Not Arriving

1. Check your spam and junk folders for mail from notifications@loomstack.app
2. Add that address to your contacts or safe-senders list
3. In Settings > Notifications > Email, confirm email delivery is on and check the digest setting — if you selected “Daily digest,” individual emails are intentionally held until the digest hour
4. Verify your email address under Settings > Account. A bounced address gets automatically suspended after repeated failures; if you see a red Delivery suspended banner, fix the address and click Resume delivery
5. On a company domain, ask IT to whitelist loomstack.app — corporate quarantine filters are the most common silent killer of notification email

Browser Push Notifications Not Showing

1. Click the lock icon in the address bar on app.loomstack.app and set Notifications to Allow
2. Check your operating system’s focus mode: Windows Focus Assist and macOS Do Not Disturb both suppress browser push silently
3. In Settings > Notifications > Push, click Send test notification. If the test arrives but real ones don’t, your event toggles are off (see the first section)
4. Note that push only works in browsers where you’re logged in; logging out unregisters the device

Mobile Push Not Arriving

1. In your phone settings, confirm Loomstack has notification permission
2. Disable battery optimization for the Loomstack app — aggressive Android battery savers delay push by hours
3. Open the app once; a device that hasn’t synced in over 30 days is dropped from push delivery and re-registers on next launch

Slack Notifications Missing

1. Go to Settings > Integrations > Slack and confirm the connection status is Active. An expired token shows Reauthorize — click it and sign in again
2. Check that the target channel still exists; notifications to archived or renamed channels fail silently
3. In the Slack channel, type /loomstack status to verify the bot can post
4. Review per-project channel routing under Configure Notifications — a project mapped to a channel you left will deliver, but you won’t see it

Summary

Always start at the bell icon: if the notification isn’t in the in-app feed, fix your event toggles or unmute the project; if it is, debug the channel. Whitelist the sender for email, use the test button for push, and reauthorize the Slack connection if its token expired. If a single event type consistently fails across all channels, contact support with the task link and timestamp.