Troubleshooting

The problems people actually hit, and how to fix them.

Start here#

Nine out of ten problems are one of two things:

1. Ledra's role is too low. Server Settings → Roles → drag Ledra above the roles and members it manages.
2. Ledra lacks a permission in that specific channel. A server-wide grant can be overridden per channel.

Then run /settings view — it shows your whole configuration at once, and most gaps are visible there.

Commands do not appear#

Right after inviting. Discord takes a few minutes to distribute a new bot's commands. Fully close and reopen Discord (not just the window — quit the app), then try again.

Still missing after an hour. The bot may have been invited without the applications.commands scope. Re-invite it with the official link.

Some commands are missing, others work. That is not a bug — commands you lack the level for are still visible but refuse to run. Check with /permissions check.

"You do not have permission to use this command"#

Run:

/permissions check member:@You

That shows your resolved level and how you got it. Compare against the permission matrix.

Common causes:

• Your staff role has no configured level and no matching Discord permission. Fix: /permissions set role:@YourRole level:moderator
• You are trying /permissions set level:admin without being the server owner. Only the owner can grant admin.
• You are using a server-only command in a DM.

"I am not allowed to …" / missing permission#

Ledra checks its own permissions in the exact channel before acting, and names what is missing.

1. Check the channel's permission overrides, not just the server-wide role
2. Category overrides cascade to channels inside them
3. A deny on @everyone in one channel beats a server-wide allow

Moderation refuses to act#

"…has a role equal to or higher than mine." Ledra's role is too low. Move it above the target's highest role.

"…has the same or a higher staff level than you." Working as designed. Moderators cannot action peers or superiors. An admin or the owner has to do it.

"The server owner is protected." Nobody can action the owner through Ledra. Ever.

"You cannot kick yourself." Also by design.

Join roles are not applied#

Check in order:

1. /joinrole list — is the role actually configured?
2. Is Ledra's role above the role being granted?
3. Does Ledra have Manage Roles?
4. Does the role grant Administrator? Those are blocked permanently, and re-checked at every join — even if the role was harmless when you added it.
5. Is it an integration role? Those can never be assigned by anyone.

Role menu buttons do nothing#

Same causes as join roles — almost always role position. Fix the position and the existing buttons start working again; no republish needed.

"This role no longer exists" — someone deleted the role. Remove it from the menu with /rolemenu remove and republish.

Welcome messages are not sent#

/welcome status

It reports enabled only when a channel and a message are both set.

• No channel → /welcome channel channel:#welcome
• No message → /welcome message text:…
• Disabled → /welcome toggle enabled:true
• Channel deleted → set a new one

If Ledra cannot see or post in the channel, it stays silent. Check the channel's permissions.

It sends as plain text although I chose an embed. Ledra lacks Embed Links there and fell back rather than posting nothing.

Nothing appears in my log channel#

1. /logging status — is the category configured?
2. Does the category cover the event you expect? A member joining is members, not messages. See the category table.
3. Was the channel deleted? Point it somewhere new with /logging set.

Message edits and deletions are missing specifically. Bot messages are never logged, and an edit that only resolves a link preview is not a real edit.

AutoMod is not doing anything#

Three switches, all of which must be right:

/automod status

1. Is the main switch on? /automod toggle enabled:true
2. Is the rule on? /automod rule rule:spam enabled:true
3. Is the action none? That logs only, by design.

Then check exemptions — /automod exempt list. If you are staff and set /automod exemptlevel level:moderator, AutoMod will never act on you. Test with a non-staff account.

AutoMod is too aggressive#

/automod rule rule:caps enabled:true action:delete
/automod limits caps_percentage:85 caps_min_length:25

Lower the action first, then loosen thresholds. Exempt a channel where the rule does not belong:

/automod exempt add channel:#memes

Reminders never arrive#

• Was the channel deleted and your DMs closed? Then it was dropped. Open DMs from server members in Discord's privacy settings.
• Did you cancel it? /reminders list shows what is still pending.
• Marked "Delivered late"? Ledra was offline when it came due and delivered it at the next start. Working as intended.

Announcements stopped#

Automatically disabled. The channel was deleted or Ledra lost write access. A note went to your moderation log. Fix access, then /announce toggle announcement_id:X enabled:true.

Posting at the wrong time. Your server time zone is probably still UTC:

/settings timezone name:Europe/Berlin

It did not catch up after downtime. Correct — missed announcements are skipped, never replayed.

/purge deletes fewer messages than I asked#

amount is how many messages are examined, not deleted. With member: set, only that member's are removed from those examined.

Discord also forbids bulk-deleting messages older than 14 days.

An error with a reference ID#

An unexpected error. The ID identifies that exact event in Ledra's logs. Send it to support with what you were doing — with the ID, the cause can be found directly.

Still stuck?#

Support