Troubleshooting

The request costs more credits than the server has left.

→Buy a top-up or upgrade from the buttons on the error, or narrow the request so it costs less. After buying a top-up, run /usage and apply it to this server — a purchase belongs to you until you choose where it goes.

One member can only spend so many of the server's shared credits in a day, so a single account can't empty the balance for everyone.

→Wait for the daily reset named in the message, or ask an admin. This is per person, so other members are unaffected.

Every automatic run has a standing credit cap. The quality you picked costs more than that cap allows even at its smallest size.

→Run the command again with max_credits set to at least the minimum the message names.

An internal cost safeguard stopped the request. Your credit balance was not touched.

→Try again later, use your own API key, or report it in the support server — this one is worth telling me about.

Model quality is part of the plan, not something credits buy. Balanced needs Pro; Deep needs Scale.

→Pick a quality the plan includes, or upgrade the server.

Server-wide summaries, live channels, presets, and welcome summaries are plan features. Buying credits does not unlock them.

→Upgrade the server from the button on the error.

You've used every schedule or live channel the plan includes.

→Remove one you no longer need, or upgrade for a higher limit.

Without a subscription a server gets three /ask or @mention replies in total. Catch-ups keep working while it has credits.

→Subscribe to keep asking questions. A top-up adds credits but won't unlock this.

The bot's own provider wallet hit its daily ceiling. This is separate from your server's credits and resets at midnight UTC.

→Try again tomorrow, or use your own API key in the meantime.

Calls paid for by Summary Bot are paused. Your credits have not changed, and requests using a personal key still work.

→Try again later, or add your own API key.

Agent mentions are rate limited per person and channel.

→Wait about a minute and mention it again.

The bot only summarizes channels you can already see yourself. This is the check that makes it safe to install.

→Pick a channel you have access to.

You can see the channel, but the bot is missing permissions there.

→Ask an admin to grant it View Channel and Read Message History in that channel. /setup shows exactly what's missing.

It can read the channel but has no Send Messages there, so the summary has nowhere to go.

→Ask an admin to grant Send Messages in that channel.

Posting a summary as a thread needs the Create Public Threads permission.

→Ask an admin to grant it, or turn threads off in /settings.

Agent conversations live in a visible thread, and this channel doesn't let you create one.

→Mention the bot in a channel where you can create public threads.

The agent's write tools never act somewhere you couldn't post yourself.

→Choose a channel where you have Send Messages.

You tried to change something shared by everyone in the server.

→Ask an admin, or make the change just for yourself instead.

An admin turned on the Manage Server requirement for every summary here.

→Ask an admin to run it, or to change /privacy restrict.

An admin has excluded the channel from summarization entirely. This applies to admins too.

→An admin can change it with /privacy channel.

Your Discord privacy settings block direct messages from members of this server.

→Turn on “Allow direct messages from server members” in that server's privacy settings, then try again.

No messages were found in the range you asked for. Usually the range is narrower than you meant, or everyone in it opted out.

→Widen the range, or pick a different channel.

The value in since or until wasn't a date or time it could read.

→Try “3 hours”, “yesterday”, “since monday”, or “jan 5 2pm”.

Timezones have to be IANA names, which are the only kind that resolve unambiguously.

→Use the Region/City form: America/New_York, Europe/London, Asia/Kolkata.

You already have a summary running. They queue badly, so only one runs at a time per person.

→Give it a few seconds and try again.

The provider says the key is invalid, revoked, or expired.

→Run /setapikey with a fresh key, or /removeapikey to go back to the server's credits.

The key is valid, but the provider declined the request for lack of funds.

→Add billing on the provider's side, or remove the key with /removeapikey.

The server's credits can't cover the request and there's no key to fall back on.

→Top up, upgrade, or add a key with /setapikey.

The stored key can no longer be decrypted. This happens when the bot's own credentials are rotated.

→Run /setapikey to add it again. Nothing else was lost.

The request failed at the provider, not in the bot. You were not charged for work that didn't happen.

→Try again shortly.

The provider didn't respond in time.

→Try again, or use a smaller range for a faster result.

The provider's safety systems refused the content. It is occasionally a false positive.

→Try a narrower range or a different summary style.

The provider is throttling requests right now.

→Try again in a moment — this usually clears within a minute.

The AI work finished and spent credits, but delivery failed. The message tells you exactly what was spent and what's left, and it won't retry on its own.

→Check Send Messages and Embed Links on the destination, then run it again.

The sbp1:… code couldn't be read. Usually it was truncated when copied.

→Ask whoever shared it to run /preset export again and copy the whole line.

Preset names have to be unique.

→Pick a different name, or delete the existing one with /preset delete.

It wasn't among your presets or the server's.

→Run /preset list to see what's available.

It was removed, or it belongs to a different server.

→Run /schedule list to see what's actually set up.

This is a bug, not something you did wrong. It's already been logged.

→Press Report on the message to send the details, or quote the trace id in the support server.