A scheduled notification uses the same source, events, filters, destination, and card choices as a real-time notification rule. The destination can be a connected server channel or one linked Discord member's direct messages. The difference is what it sends: matching activity waits in the rule's queue and is delivered as a grouped card at the next scheduled run.

Set the schedule

In a notification rule, choose Scheduled, then select:

  • Hourly for one delivery every hour.
  • Daily for one delivery each day at the selected local time.
  • Weekdays for one delivery Monday through Friday at the selected local time.
  • Weekly for one delivery on the selected weekday and local time.

Every schedule requires an IANA timezone, such as Europe/Warsaw. Daily, Weekdays, and Weekly schedules accept minute-level local time. Weekly also requires a weekday.

Understand what is included

Only activity that matches the enabled rule is queued. Page creations, page updates, and comments remain distinct events in the grouped result. Activity that does not match the source, event types, or filters is not included.

The queue records which events matched, without saving their page or comment text. When the schedule runs, the app reads the current Confluence content for each queued event. If a page or comment changed again, the grouped card shows its latest content. If a page or comment is missing or access is denied, the affected event is marked failed in History and is not included in the Discord card. A temporary Confluence error leaves the event queued for the next scheduled run.

The runner sends as many grouped messages as needed to process the queue. Each message fits complete events within Discord's component and text limits, so it can contain fewer rows when the text is longer. Eight events is not a total delivery limit. Events are completed only after their message succeeds; a failed message does not consume later, unattempted events.

Scheduled notifications differ from scheduled summaries. A scheduled notification groups matching activity that occurred. A summary queries fresh Confluence pages when it runs.

Verify a scheduled rule

  1. Review the timezone, cadence, destination, and enabled events.
  2. Use Send preview to verify the card and destination. A preview does not consume queued activity.
  3. Save and enable the rule.
  4. After the first due time, open History and confirm the delivery.

If no matching activity occurred, there is nothing to group. If a due delivery fails, use History for its recorded status and recovery guidance rather than creating a second rule.

RelatedSend fresh page summaries