Troubleshooting

Use this page when Lockie is online but something is not working as expected.

Bot looks online but does not respond

Check these first:

1. Lockie can view and send messages in the channel.
2. Lockie's role is not blocked by channel overrides.
3. Your role can use slash commands in that channel.
4. The command is enabled for your server.

Try:

/ping

If /ping works in one channel but not another, the issue is probably channel permissions.

Slash commands are missing

This is usually caused by one of these:

• Lockie was invited without the applications.commands scope.
• Discord has not refreshed slash commands yet.
• The command is restricted by Discord permissions.
• You are viewing a server where Lockie is not installed.

Fix:

1. Re-invite using https://lockieapp.ca/invite
2. Keep the slash command scope enabled.
3. Wait a minute.
4. Restart Discord or refresh the web client.
5. Type / and search for Lockie commands again.

Server is missing from the Dashboard

Make sure:

• You are signed into the correct Discord account.
• You have permission to manage the server.
• Lockie is in the server.
• Your browser did not block the login session.

Try signing out, signing back in, and refreshing the server selector.

Logs are not posting

Checklist:

1. The correct log channel is selected on the Dashboard.
2. Lockie can View Channel, Send Messages, Embed Links, and Read Message History.
3. The feature that should create the log is enabled.
4. The action actually happened after logs were configured.

If the log uses buttons, components, or rich embeds, Lockie also needs permission to send embeds in that channel.

Protection modules are not triggering

Check:

1. The module is enabled on the Dashboard.
2. The channel is not allowlisted or exempt.
3. The user's role is not exempt.
4. Lockie has Manage Messages if the action deletes content.
5. Lockie has Moderate Members, Kick Members, or Ban Members if the action uses those moderation tools.
6. The content matches the type of protection you enabled.

For Anti-Scam and Anti-Dox, also check whitelist and blacklist entries. Standard servers may have a 15 entry limit per whitelist and blacklist control.

Too many false positives

Start with logs. They usually show what triggered the action.

Common fixes:

• Add trusted domains or phrases to the whitelist.
• Remove overly broad blacklist entries.
• Exempt staff channels where testing happens.
• Exempt staff roles if they need to share examples for moderation.
• Lower the action severity while tuning, such as log only instead of timeout or ban.

Avoid turning off logs while tuning, because logs are the easiest way to understand what Lockie is catching.

Anti-Scam whitelist or blacklist will not save

Check:

• You are below your plan limit.
• The entry is not empty.
• The entry is not already saved.
• You have permission to edit that server's settings.

Standard servers are usually limited to 15 whitelist entries and 15 blacklist entries for Anti-Scam controls. Premium may allow more depending on the plan.

Anti-Dox whitelist or blacklist will not save

Check:

• You are below your plan limit.
• The entry is not too broad.
• The entry is not already saved.
• You have permission to edit that server's settings.

Standard servers are usually limited to 15 whitelist entries and 15 blacklist entries for Anti-Dox controls. Premium may allow more depending on the plan.

Maintenance Mode or locks are not applying

Check:

1. Lockie has Manage Channels.
2. Lockie's role is high enough.
3. The configured lock role still exists.
4. The channel has no unusual overrides blocking the change.
5. You are using the correct lock type for your server.

Lockie remembers channel permissions during improved lock flows. If an unlock does not restore access, check whether another role or manual channel override is still blocking members.

Ban Lock or Kick Lock warning is showing

A lock alert means a strong locking behavior may be enabled for the server.

Check the Locking plugin in the Dashboard and turn off the lock behavior you no longer need. Use this carefully during incidents, because kick and ban related locks can affect real members if left enabled.

Massban is slow or partially failed

Mass actions can take time because Discord rate limits moderation actions.

Check the final summary for:

• Successful
• Failed or skipped
• Delete history setting
• Reason
• Time taken

Common reasons for skipped or failed bans:

• Lockie's role is lower than the target.
• The target is already banned.
• Discord rejected the action.
• The member ID was invalid.
• The bot is missing Ban Members.

Masspurge did not delete everything

Masspurge can be limited by Discord message rules and channel access.

Check:

• Lockie can View Channel and Manage Messages in every target channel.
• The selected user actually has messages in those channels.
• The messages are not too old for Discord bulk delete behavior.
• The target channels are text or announcement/news channels.

Custom App Profile is not updating

Check:

• The server has Premium.
• The image file is valid.
• The avatar or banner meets Discord limits.
• You saved changes on the correct server.
• The dashboard finished uploading before you left the page.

If the old image still appears, refresh Discord or wait for caching to update.

I see 403 Missing Access

Lockie cannot access the channel, message, member, or server resource.

Fix:

• Give Lockie access to the channel.
• Check channel overrides.
• Make sure Lockie is still in the server.

I see 50013 Missing Permissions

Lockie is missing a required permission or its role is too low.

Fix:

• Move Lockie's role above the target user's highest role.
• Grant the required permission.
• Check channel-specific overrides.

I see 429 rate limit warnings

Discord is slowing down repeated actions.

Lockie will usually retry or continue safely, but frequent edits can trigger longer cooldowns.

To reduce this:

• Avoid repeatedly locking and unlocking the same channels.
• Avoid editing the same message too often.
• Let mass actions finish before starting another one.

Still stuck?

Open a support ticket and include:

• What you were trying to do
• The server ID
• The channel ID, if relevant
• The command or dashboard section used
• A screenshot of the error or log
• Whether it happens only on one server or everywhere

Support server:

• https://discord.gg/dK45FDUsAJ