Confluence Watch Rules – Global Notification Settings – Can Digest Frequency Override @Mention Alerts?
0 reputation · 17 Nov 2020, 05:55 UTC
0 reputation · 17 Nov 2020, 05:55 UTC
Determine whether Confluence’s digest‑based notification preference can suppress instant alerts triggered by @mentions when a user is watching a page or space.
Given the documented ability to set a daily digest for watch rules, does the presence of an @mention on a watched page still trigger an immediate email, or can the digest preference be honored for both content changes and mentions?
35275 reputation · 17 Nov 2020, 12:45 UTC
No. In standard Confluence behavior, setting a page or space watch to Daily Digest does not override @mention alerts. Direct mentions are treated as high-priority events and are normally sent as immediate emails, while the digest governs routine content changes such as edits and new attachments.
Confirmed: Watch rules with a digest setting control the cadence for general page updates. If a colleague edits a watched page without mentioning you, that notification is batched into the next digest.
Likely explanation: @mentions bypass the digest queue because they represent direct user-to-user communication. Atlassian’s notification model gives mentions higher priority than ambient content updates. There is no native user-level toggle that forces @mention emails to respect a digest frequency.
Because Atlassian periodically adjusts notification behavior and delivery internals differ by deployment, verify in your own instance:
Before testing, confirm outbound mail is enabled in Administration → General Configuration → Mail (or the Cloud equivalent). If global email is disabled, both digests and mentions are suppressed, which can mask the real behavior.
Confluence Cloud and recent Data Center/Server versions share the same fundamental priority model: mentions are immediate. On Server/Data Center, however, a stalled mail queue or scheduled notification job can delay even high-priority mentions. That delay may resemble digest batching but is actually a delivery-pipeline issue rather than a watch-rule override.
Which Confluence edition and version are you running (Cloud, Data Center, or a specific Server release)? That determines whether you should inspect the Cloud mail queue or the Server notification/mail server logs when verifying timing.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.