Ordered by how often each one turns out to be the answer.
Cause: role hierarchy, nine times out of ten.
A bot can only manage roles that sit below its own highest role. If Cloudy's role is under the role your panel hands out, the assignment fails and Discord returns a generic permission error the bot cannot translate into anything more helpful.
Fix: Server Settings → Roles, drag Cloudy's role above every role it should manage.
Affects: reaction roles, verification, auto-roles, birthday role, automation role actions.
Cause: the bot cannot post there.
Check, in the channel's permission overwrites (not just the role's global permissions):
A channel-level deny beats a role-level allow. This is invisible from the dashboard, which is why a correctly configured plugin can still produce nothing.
Cause: a missing privileged intent.
| Intent | Without it |
|---|---|
| Server Members | No joins/leaves → no welcome, goodbye, auto-roles, verification, birthday role |
| Message Content | No message text → no AutoMod, leveling, custom commands, sticky messages |
The hosted Cloudy bot has both. If you run a custom bot, enable them in the Discord Developer Portal → your application → Bot → Privileged Gateway Intents. The bot reconnects on its own within a minute.
Cause: Discord's registration delay, or the plugin is off.
Commands are registered when a plugin is enabled and removed when it is disabled. Discord then takes one to two minutes to show them. Also try fully restarting your Discord client — its command cache is aggressive.
Cause: normal — or the bot cannot post in the target channel.
Panels are posted by the bot, not the dashboard. Expect about 30 seconds, during which the list shows a posting… badge. If the badge never clears, the bot cannot write to that channel — check the permissions above.
Work through these in order:
The save bar at the bottom of the page is not decorative. Unsaved changes reach nothing.
The header toggle is separate from the settings below it.
Premium plugins with a lapsed license count as inactive, and the page shows a lock bar.
Panel edits go through the bot.
The server has no active license, or the license was detached. Open the server's Premium page or your
/profile to check. Your configuration is intact either way — see
What Premium unlocks.
The settings could not be read — usually a transient backend problem. Use Try again.
The form deliberately refuses to render defaults in this state: saving them would overwrite your real configuration with blanks.
Cause: the wrong username, almost always.
Enter the URL slug, not the display name — twitch.tv/shroud means shroud. A wrong slug tracks
nothing and produces no error.
Also confirm the per-platform toggle is on. Twitch, Kick and YouTube each have their own switch.
You need to be the owner, or have Administrator or Manage Server on it. Cloudy also caches your guild list briefly — use the refresh button in the server selector after a permission change.
Cause: the role permission mode is inverted.
Cause: the bot lacks Manage Messages or Read Message History in that channel, so it can post the new copy but not delete the old one.
Cause: missing Move Members. The channel is created but the member cannot be moved into it.
Ask in the Cloudy Discord. Bring:
That last one splits the problem in half: if the action is in the log, Cloudy did it and the question is why. If it is not, Cloudy never ran — and the answer is almost always in this page.