Scheduled Summaries
Scheduled summaries post a fresh snapshot of what matches right now.
Not the same as scheduled changes
Scheduled summaries rebuild from the current matching items. Notification-rule Scheduled changes sends what changed since the last run.
Build the summary
- Open Scheduled Summaries.
- Click New summary.
- Choose the source, destination, and cadence.
- Pick the row fields people should scan first.
- If the list uses Details, choose the fields for the opened details card too.
- Save the summary and wait for the next run.
Choose the right cadence
| Cadence | Best fit |
|---|---|
| Daily | Morning rollups, handoffs, and review queues |
| Hourly | Faster-moving queues that need fresher snapshots |
If you move a daily run later
Moving a daily summary later to an hour that has not happened yet can make it run again that same day. Moving it earlier waits until the next day.
Add extra controls only when they help
- Filters narrow what counts at run time.
- Summary item details makes the opened card more useful without crowding the list.
- Quick actions and row mentions work only on database-backed summaries.
- Additional mentions are useful only when a fixed group should always be pinged.
Common gotchas
Scheduled summaries are separate from page lists. Database-only features such as quick actions and row mentions do not appear on All pages or Selected pages summaries. Each Discord message shows up to 10 matching items.
Need limits or exact behavior? Open Scheduled Summaries.