Weekly Digest

The digest is a short, automatic roundup of what your community saved and solved over the past week, posted once a week to a channel you choose. It exists so the answer someone posted on a Tuesday doesn’t only reach the people who happened to be online that day.

Setting it up

/digest action:setup day:Friday hour:17 timezone:America/New_York

Requires Manage Server. day, hour, and timezone are all optional on setup:

Option	What it means	If you omit it
day	Day of the week the digest posts	Keeps the current value, or defaults to Tuesday if never set
hour	Local hour, 0-23, in the timezone below	Keeps the current value, or defaults to 12 (noon) if never set
timezone	An IANA timezone name, e.g. America/New_York, Europe/London, Asia/Tokyo, UTC	Keeps the current value, or defaults to UTC if never set

The digest is enabled in whatever channel you ran /digest action:setup in - that becomes the digest channel. Running /digest action:setup again from a different channel moves it there.

Timezone must be a real IANA name, not an abbreviation - America/Chicago works, CST does not. An invalid name is rejected with an error before anything is saved.

What’s actually in a digest

Each digest is built from the trailing seven days and can contain up to three sections, each capped at five items:

• New wiki entries - the top pushpin//wiki save captures from the week, ranked by reaction count (highest first).
• Questions answered - new Q&A pairs captured with /solve during the week.
• Still unresolved - active (non-archived) threads in opted-in channels that don’t have a /solve pair yet, capped at five.

Each item is a clickable link back to its source message. If nothing new happened - no saves, no solves, no open threads meeting the criteria - the digest still posts, but with a plain “a quiet week” message instead of empty sections.

One thing worth knowing: only content from channels readable by everyone in the server (the @everyone role) can appear in a digest, even if the source channel is opted in. If you’ve opted in a restricted channel that only some roles can see, its saves and solved questions are automatically left out of the digest - the digest is designed to never leak restricted content to a wider audience than it already has. The digest message itself doesn’t include raw counts or statistics beyond the sections above; that data is only used internally.

Where it posts

In the channel you ran /digest action:setup in - not necessarily the same channel where the flagged content came from. A common pattern is a dedicated #weekly-digest or #announcements channel.

Posting on demand

/digest action:now

Builds and posts a digest immediately, covering the trailing seven days from the moment you run it. This is separate from the scheduled weekly post - it doesn’t count as that week’s scheduled digest, and it doesn’t reset or affect your day/hour/timezone settings.

/digest action:now is limited to once per hour, per server. If you’ve triggered it recently, you’ll be told to try again later. If the digest fails to post (see below), the attempt doesn’t count against this cooldown, so you can retry right away.

Honest failure behavior

If the digest channel gets deleted, or the bot loses permission to send messages there, the digest simply doesn’t post - there’s no error DM, no fallback channel. For the scheduled weekly digest, this isn’t treated as a missed week: the bot checks hourly, and if that week’s digest hasn’t successfully posted yet, it tries again on the next hourly check. A digest only counts as “done for the week” once it actually sends. That said, the catch-up window isn’t unlimited - if the bot is offline or failing for more than seven days straight, that week’s digest is skipped rather than posted very late.

Turning it off

/digest action:off

Disables the weekly digest. Nothing already posted is affected, and your day/hour/timezone settings are kept in case you turn it back on later with /digest action:setup.