Troubleshooting
DocsResources

Troubleshooting

Diagnose command, permission, hierarchy, message, and integration failures.

Command not found

  • Run ,prefix to confirm the server prefix.
  • Use ,help <command> or the Commands page to confirm the exact command name.
  • Check whether the command is server-only or requires another restriction shown on its command card.
  • Do not assume a feature card on the landing page guarantees a command with the same name.

Permission denied

Check the command's user permissions and bot permissions separately. Then inspect channel overwrites and role hierarchy. The permissions command can show a member's effective permissions in a channel.

moderation

,permissions

Lists which permissions a member has and does not have in a channel, combining their server-wide permissions with that channel's overwrites. Defaults to you in the current channel.

,permissions [user] [channel]
Example,permissions @user #channel
Arguments
userOptional
channelOptional
User permissionsManage Channels, Manage Roles
Open in command browser
Permissions and HierarchyUnderstand user permissions, bot permissions, fake permissions, and Discord hierarchy.

Moderation action failed

  • Move Appear's role above the target member's highest role.
  • Grant the bot permission listed on the command card.
  • Confirm the target is not the server owner and is otherwise manageable by Discord.
  • For jail, make sure jail enable has completed and the jail role sits below Appear.

A configured message is not sending

  • Confirm Appear can View Channel, Send Messages, and Embed Links where applicable.
  • Run the feature's config or list command to confirm it is enabled and points to the intended channel.
  • Use the feature's test command when one exists, such as welcome test.
  • Validate builder syntax in the Embed and C2 Builder.

A lookup or integration failed

Confirm the profile or post is public and the input matches the command usage. External services can reject requests because of deleted content, privacy settings, region restrictions, rate limits, or upstream changes.

Still stuck

Join the Appear support server and include the exact command, the response Appear returned, the relevant channel, and what you expected to happen. Avoid sharing private tokens or credentials.