Browse Help Center
Help Center
Elsewhere

Notifications Not Working

Check these five things in order. Stop when a new notification arrives in the right place.

  1. Start here

    Check the rule card

    Open Notifications and find the rule. Read its status and message.

    • Paused or Blocked: fix the problem shown on the card. Turn a Paused rule back on.
    • Off: turn it on.
    • Pending: the rule is combining changes. Check its estimated send time; each matching change to the same page or comment restarts the wait.
    • Waiting: trigger the source or event named on the card, then select Refresh status.
    • Last delivery failed: read the recorded error on the card, then open History for the attempt. Active: open History if an expected notification is missing.

    Lost access? Restore Notion access or Discord permissions.

    For a Notion page, share it again. Do not disconnect the workspace.

    Paused Release updates rule showing its source, destination, problem, fix, switch, and History button
  2. See what happened

    Check History

    Open the newest row for the event or scheduled send you expected.

    • Failed: open the row, fix the error, and try again.
    • Successful: check that it went to the right place.
    • No row: continue to step 3.
    History with one Failed update and one Successful update, including the source and time
  3. If History has no row

    Check the source

    Edit the rule. Make sure its workspace, database, or page includes the Notion content you changed. If it does, continue to step 4.

    Source selector with Database items selected Release Train selected as the Notion database
  4. Check when it runs

    Check the trigger or schedule

    • Real-time: check that the rule watches the event you triggered. For property updates, check the watched properties too. Delete events cannot use Filters that need data from the deleted page. Remove those Filters.
    • Scheduled: check the saved time. Changes made after that time take effect at the next scheduled send. If one send was missed while the rule had a problem, NotiCord sends it once after the problem is fixed.
    Real-time settings with New items and Item updates selected, Content changes and Property changes turned on, and no property limit
  5. Last check

    Check Filters

    Before testing:

    • For property updates, select the changed property or watch all properties.
    • Make sure every Filter matches.
    • Replace any value marked Unavailable.
    Test once
    1. Make one change that should match.
    2. Wait up to five minutes, or until the next scheduled time.
    3. Open History. A Successful row means it worked. Fix a Failed row. If there is no row, use support below.
    Filters with one row: Stage is Draft

Still no row in History?

Ask in Discord or email support@noticord.com.

Direct messages

If a DM did not arrive

Rule DMs and comment-mention DMs need different checks.

DM from a rule

Make sure the person is approved in Members. They do not need a linked Notion account. Fix the Failed row in the rule's History, then test again.

DM from a comment mention

In Members, make sure the person linked Notion and turned on Comment mention DMs. Test with a new mention from someone else. Old mentions are not sent later. If it fails, open the Failed row in Notification History.

If Discord cannot deliver the DM, turn on Direct messages in Content & Social for this server or all servers. See Discord's DM privacy instructions.

How long does History stay available? Some blocked sends: 30 days

While a subscription is open, expired-trial and inactive-subscription blocks stay for 30 days. Quota blocks and other rows stay until the subscription's data is deleted. Closing it stops History access immediately; its data is deleted after 30 days. Old rows do not affect your current subscription.

Support