Bot isn't reacting to my role changes

Four most common reasons:

1. The bot role sits BELOW the sync role in Discord's hierarchy. Discord doesn't let a bot grant roles that are ranked higher than its own. Move the CloudMod role to the top, right under your owner/admin role — on every sub-server. CloudMod posts ⛔ Role can't be assigned in your log when this happens; the entry repeats at most once a day per role.
2. The bot is not invited to the sub-server, or lacks Manage Roles there. Re-invite using the dashboard's invite link. A missing permission shows up in your log as Missing permission for the role in question.
3. You're in Dry-run mode (only in Network mode). The project shows Test mode, and a Dry-run active banner sits at the top of the dashboard. The bot logs everything but doesn't touch real roles. Click Go live in the banner, or switch off Dry-run mode under Project settings → Server setup.
4. The network is Paused. The bot then ignores every event for it. Turn Project active back on under Project settings → Danger zone, or click Resume network in the banner.

Let CloudMod call you

Pick an Admin role under Project settings → Admins & permissions (or with /admin setrole, or during /setup). CloudMod pings that role in the log when it needs a human — a role above CloudMod, a missing permission. At most once an hour.

The ping only reaches people if the role is mentionable: Server Settings → Roles → Allow anyone to @mention this role.

Check it yourself

• The Health Check page in the dashboard checks every server in your network: bot missing, Manage Roles missing, roles above CloudMod, deleted roles, and the log channel.
• The page shows when it was last checked. It refreshes itself at most once a day, and again after the bot's roles or permissions change. With Link or higher you can also press Check now (then wait two minutes before the next check).
• It also lists roles that carry Administrator (and @everyone, if it holds powerful permissions). If a role is meant to have it, the project owner can mark it Good, so it stops counting against the score.
• /checkperms shows, on the server you run it in, whether CloudMod has every permission it needs (admins). With a member — /checkperms @member — anyone sees whether CloudMod can change that member's roles; it can't if their highest role is level with or above CloudMod's own role.