🛟 Help Center Navigation

Help Center

💬 Discord Community ← Back to Documentation

Notifications Not Working

Use this page if a rule never sends notifications, sends them late, shows a blocked state, or a comment mention DM does not arrive.

1. Wait first

Most notifications arrive within 1 minute. Allow up to 5 minutes before troubleshooting.

If you just created the rule or triggered the event, wait before changing anything.

2. Check the notification rule list

Open Notifications in the sidebar and look at the notification rule card:

  1. Make sure the rule toggle is on
  2. Check the health state: Healthy, Waiting, Paused, Blocked, Recent failure, or Off
  3. Open History
  4. Read any issue cards, such as paused delivery failures, missing Discord permissions, or unavailable Notion source
Notification rule list showing rule cards with health states, issue cards, history links, and enable or disable toggles
Notification rule list showing rule cards with health states, issue cards, history links, and enable or disable toggles

If the rule is Blocked, follow the issue shown there first.

If the rule is Waiting, read the detail line first. It tells you which Notion change the rule is waiting for. For real-time rules, that change should produce the first Discord notification. For scheduled-change rules, that change needs to happen before the next scheduled run. Scheduled-change rules can also show whether they are still waiting for the first scheduled check or are waiting for the first sent result after a recent run.

If the rule is Paused, fix the issue shown there and turn the rule back on with its toggle. NotiCord pauses only on deterministic delivery failures, so the rule stays paused until you turn it back on. When the pause is caused by missing Discord permissions, the row can show the exact missing permissions, such as Send Messages.

If the rule sends by direct message, the pause reason can also tell you that the selected account is no longer linked or that Discord could not deliver DMs to that person.

3. Check comment mention DMs

If a linked user did not get a comment mention DM:

  1. Open Linked Accounts under Account and confirm that person is still linked
  2. Confirm Comment mention DMs is on for that linked account
  3. Open Notification History and look for a Comment Mention DM row
  4. Read the failure message there

If Notification History says that person's Discord direct messages are disabled or unavailable, ask them to allow Discord direct messages from server members or adjust their Discord privacy settings, then create a fresh new mention in Notion.

Comment mention DMs send only for new comment mentions. Turning the toggle on later does not backfill older mentions.

4. Check the rule logic

Common mismatches:

  • You tested an update, but the rule only watches New items
  • You tested a page rule New subpages event, but the page scope does not include child pages
  • You tested a property change, but the rule only watches Content edits
  • You selected specific properties, and the changed property was not one of them
  • You added an Advanced filters row, and the updated item does not match it anymore
  • A saved Status, Select, Multi-select, or People filter value no longer exists in Notion, so the editor keeps that unavailable value visible and asks you to replace it or remove the filter before preview or save

Quick test: create a minimal New items rule and then create a new item that clearly matches it.

5. Check direct-message rule delivery

If the rule sends to one linked account by direct message:

  1. Open the rule and confirm the selected account is still linked in Linked Accounts under Account
  2. Open Notification History and look for that rule's failed delivery row
  3. Read the failure message there

If the selected account is no longer linked, choose a different linked account in the rule and save again.

If Notification History says Discord could not deliver a direct message, ask that person to allow Discord direct messages from server members or adjust their Discord privacy settings, then send a fresh preview or wait for the next matching event.

6. Fix missing Discord channel permissions

If the rule shows missing Discord permissions, or the channel picker says NotiCord cannot send notifications in the selected channel yet, use Fix Missing Discord Channel Permissions.

If the target channel was deleted, moved to a type NotiCord cannot send notifications in, or the bot lost access, the rule may show Paused instead of Recent failure. Restore access or choose a working channel, then turn the rule back on.

7. Check Notion access and connection

If the source was unshared, deleted, or the workspace connection expired, the rule cannot run.

  • Make sure the page or database is still shared with NotiCord
  • Reconnect Notion if Settings says the workspace connection expired
  • If the source was removed, reselect a working source and save the rule again

Unlike Discord delivery failures, unavailable Notion sources show as Blocked and need a source fix before the rule can run again.

Use Give NotiCord Access in Notion for the sharing flow.

⚠️ Disconnecting Notion removes rules
If you disconnect the Notion workspace, existing notification rules for this subscription are removed.

Still stuck? Join the Discord community or email support@noticord.com.

Support