Documentation

Schedules, live & welcomes

Three ways a summary can arrive without anyone running a command — and, more importantly, the caps that make it safe to leave them running. Every automatic feature has a spending ceiling you set yourself.

Scheduled summaries

A schedule runs a summary on its own, daily or on a chosen weekday, and delivers it to your DMs or into a channel.

/schedule add every:Every day at:09:00

The hour is in your timezone once you've set one with /settings.

deliverdefault: DM: To your DMsis private, needs no permissions, and is nobody else's business. To a channel is public and needs Manage Server.
sourcedefault: this channel: Which channel it summarizes.
server_widedefault: off: Summarize the whole readable server instead of one channel. Pro and Scale.
tierdefault: Fast: Which quality runs it. Higher quality costs more per run, every run, forever — this is the setting to think twice about.
max_creditsdefault: 3,000: The standing cap for one run. See below.

Plan	Schedules	Server-wide schedules
Free trial	—	—
Starter	1	—
Pro	5	Yes
Scale	25	Yes

Why Starter includes exactly one

A daily digest of a 1,000-message channel costs roughly 30,000 credits a month against Starter's 50,000. Two would run the plan dry mid-month and start failing every morning. The limits are sized against the allowance on purpose, so a schedule you set up keeps working.

/schedule list shows what's set up here, /schedule off stops one, and /schedule run runs one immediately so you can see what it produces before committing to it every morning. That last one is worth doing once.

Live channel summaries

/live on keeps a single message current in a busy channel. Rather than posting a new summary every hour, it edits the same one as the conversation builds.

/live on channel:#general messages:100

It updates when enough new messages have arrived — not on a timer. The bot counts messages as they come in rather than polling Discord, so a channel that goes quiet costs nothing at all.

messagesdefault: 50: New messages needed before it refreshes, between 25 and 500. Pro's floor is 50; Scale's is 25.
post_todefault: the source channel: Where the single live message lives. Pointing it at a quieter channel is often nicer.
Minimum gap15 minutes: Even in a firehose, it will not update more than once every 15 minutes.

Plan	Live channels	Message floor
Free trial	—	—
Starter	—	—
Pro	1	50
Scale	5	25

A live channel is a standing bill

Set the threshold to match how much you actually want to spend. A busy channel at messages:25 will update far more often — and cost far more — than the same channel at messages:200.

/live status lists what's running. Both on and off need Manage Server.

Welcome summaries

On Pro and Scale, a new member can get a short DM bringing them up to speed — drawn only from channels that member can already read, after their roles are applied.

It waits for membership screening to finish rather than firing the moment someone joins. In a gated server a brand-new member can only see the rules channel, and a tour of #rules helps nobody.
It skips servers where there isn't enough to say — there are minimums for messages, distinct participants, and actual content before one is sent at all.
Daily caps: 25 a day on Pro, 100 a day on Scale. A raid can't drain a server's credits through the front door.
Any member can turn these off for themselves everywhere with /privacy welcome. That switch outranks every server's setting — someone in a dozen communities shouldn't have to mute them one at a time.

Welcome summaries are off until an admin enables them in /setup.

Standing credit caps

A person running /catchup can be asked “this costs 8,000 credits, continue?”. A schedule firing at 09:00 has nobody at the keyboard, so it uses a standing cap you agree to in advance instead.

max_creditsdefault: 3,000: The most one automatic run may spend. From 3,000 to 100,000. You confirm the cap once, when you set the schedule up.
If a run would cost more: It doesn't skip and it doesn't overspend. It keeps the newest messages that fit inside the cap and summarizes those, so you still get the most recent context.
Higher quality needs a higher cap: Deep starts at 800 credits per run before it reads anything. If your cap is below a tier's minimum, the bot refuses at setup time and tells you the number to use — it will not accept a schedule that could never run.

The same cap applies to live summaries and welcome DMs. Nothing automatic spends more than its cap, ever.

When an automatic run fails

The worst possible behaviour for a standing order is to fail quietly and still look enabled. This is treated as a bug class, not an edge case.

Out of credits, plan downgraded, or channel blocked — the schedule stops immediately and says so. It does not keep silently failing every morning.
Nothing to summarize is the one silent case. A quiet day produces no DM rather than a message telling you the channel was quiet.
Delivery failed after the work was done— you get told exactly what was spent and what's left, and it will not retry on its own. Usually the destination lost Send Messages or Embed Links.

If a schedule stopped and you want to know why, /schedule list shows its current state, and any error the bot showed you carries a code you can look up in Troubleshooting.