Notifications do not arrive

Check these in order:

  1. The rule is enabled and its health is not paused or blocked.
  2. The expected event is selected: new page, update, or comment.
  3. The page belongs to the rule's source and matches its filters.
  4. The selected destination is still available. For a channel, confirm it does not show Needs access or Unavailable.
  5. The production license is active.
  6. History does not show an unlicensed, permission, source-mapping, or send failure.

Remember that global rules can apply across the site, while space rules apply only to their space.

A channel destination is blocked

Open the rule editor and review the destination. Restore the permissions named under Needs access, or restore View Channel first for an unavailable channel. Select Recheck permissions, then send a preview before relying on live activity.

A direct-message recipient is unavailable

Edit the rule or summary and search for the recipient again. The person must have a connected Discord account and be visible through the administrator's current Confluence access. Choose another valid recipient if the prior link is no longer available.

A scheduled notification did not send

Confirm that the rule is enabled, the timezone and due time are correct, and matching activity occurred after the rule became active. A scheduled notification sends queued matching activity, not a fresh list of pages.

Use the rule's History to inspect the run. Sending a preview verifies the destination and card but does not consume or create queued activity.

A scheduled summary did not send

Check that the summary is enabled, its destination is available, and its source and filters can return pages. Select Send now to verify the destination without waiting for the next due time. Empty results are recorded explicitly.

History says Send failed

Check the failure detail, destination access, and Discord channel or direct message. Failed attempts are not automatically retried. Before using Send now or triggering another matching change, check whether the message already exists because Discord may have accepted it before the app recorded completion.

Channel recoveryFix connection and channel access