Troubleshooting

Four checks account for nearly everything, and they take under a minute between them. Work through these before reading the sections below.

• Is the feature switched on and saved? Every feature has its own switch on its dashboard page, and settings apply when saved, not when typed.
• Does your plan include it? Nothing is deleted when a trial or subscription ends: paid features stop running and keep their settings, visible but read-only, and pick back up when you subscribe again. A list over your plan's limit keeps the oldest entries and pauses the rest.
• Can Unum see and post in the channel concerned? Channel overrides beat server-wide permissions.
• Is the service up? The status page at /status shows current incidents and maintenance.

Check the member list first. If Unum is not in the server at all, it was removed and needs adding again. The invite flow is on every page of this site.

If it is in the server but shows as offline, check /status before anything else. If we are up and your server is the only one affected, the next question is whether you are running a custom bot: a custom bot in the error state is your server going quiet while the shared bot is perfectly healthy.

Commands are registered with Discord when the bot connects, and Discord decides when your client sees them. A short delay is normal and nothing is wrong.

1. 01Wait a minute, then type a slash in the message box again.
2. 02Restart your Discord client. This forces it to refetch the command list, and it fixes most cases.
3. 03Check that your role has Use Application Commands in that channel. A channel override can hide commands from the people who need them.
4. 04Check on another device or in the browser. If commands are there and not in your desktop client, it is a client cache, not your server.

If you run a custom bot, its commands are registered against your own application when it connects. A custom bot stuck on Connection error never gets that far, so fix the connection first.

This covers welcome messages, stream notifications, scheduled messages, logs and automation replies. They all fail for the same handful of reasons.

• The target channel was deleted or renamed, and the feature still points at the old one. Reselect the channel and save.
• Unum lacks View Channel, Send Messages or Embed Links there. An embed needs Embed Links specifically, so a feature that posts plain text can work in a channel where an embed will not.
• The feature is switched off, or the settings were changed but never saved.
• Your plan no longer includes it. Stream notifications, scheduled messages and automations are Plus features.
• For anything driven by a stream platform, the platform account is not connected, or the connection needs reauthorising.

If logging is enabled for the relevant category, the Logs page tells you whether Unum saw the event at all. An event that was recorded but produced no post is a permissions or configuration problem; an event that was never recorded means the bot did not receive it.

This is almost always role hierarchy. Unum can only manage roles below its own highest role, and can only moderate members whose highest role sits below its own. Having Manage Roles is not enough on its own.

• Drag Unum's role above every role it hands out: level roles, live roles, subscriber roles and role menu roles.
• Server owners cannot be actioned by any bot, whatever the hierarchy says.
• Roles managed by an integration, including another bot or a platform subscription, cannot be assigned by anyone. If a role has a lock next to it in Discord, use a separate role instead.
• If it fails for one member and works for everyone else, compare that member’s highest role with Unum’s.

Permissions and role hierarchy goes through this in full, including which permission each kind of feature needs.

Rules fail quietly by design. A condition that is not met is a rule deciding not to act, which looks identical to a rule that is broken. Check these in order.

• The rule shows Disabled in the list. Switch it to Enabled.
• A condition cannot be met by that trigger. Conditions only see what their trigger provides, so a bits or raid condition on a Discord trigger will never be true.
• The cooldown has not elapsed. A global cooldown blocks the rule for everyone, not just the person who triggered it last.
• Another rule acted first. Priority runs lowest first, and a rule that deletes the triggering message leaves nothing for a later rule to read.
• The action itself was refused. Role and moderation actions need the permission and the hierarchy; the rest of the rule carries on regardless.

The page shows the reason Discord gave. Two causes account for nearly all of them.

The token is no longer valid

It was reset in the Developer Portal, or Discord invalidated it because it was exposed. Reset it again to get a working one, paste it into Re-enter bot token and click Retry Connection.

A privileged intent is not enabled

All three are required: Presence Intent, Server Members Intent and Message Content Intent. Enable the missing one in the Bot section of the Developer Portal, then retry.

If none of the above fits, the status page at /status is the first stop. It lists current incidents, maintenance and the health of each part of the service, so you can tell in seconds whether the problem is ours.

The support server

The quickest route for setup, commands and dashboard questions. The team is there, and so are other server owners who have probably hit the same thing.

support@unumbot.com

For account and billing questions, or anything you would rather not post in a public channel. Include your server's name and what you have already tried.