Discord Slash Commands Not Showing Up or "Interaction Failed"? How to Fix It in 2026

If your bot's slash commands aren't showing up, re-invite the bot using the applications.commands scope and wait a few minutes for Discord to register them. If commands appear but throw "This interaction failed," the bot is usually offline, missing the Use Application Commands permission, or its host is down. Fix both by checking the bot's invite scope, role permissions, and online status.

Slash commands are the modern way to use Discord bots: you type / and a menu of commands pops up. When they vanish from that menu, or when clicking one returns a red "This interaction failed" message, it almost always comes down to one of three causes. None of them require coding, and all of them are fixable in a few minutes. Here is exactly what is going wrong and how to fix it.

If you are new to how these work, our explainer on what Discord slash commands are covers the basics. This guide is for when they break.

Why slash commands disappear or fail: the 3 real causes

Before you start changing settings at random, it helps to know what Discord is actually doing behind the scenes. There are only three things that go wrong:

1. The bot was invited without the applications.commands scope. This is the single most common cause of "no commands showing up." If a bot was added with an old invite link or only the basic bot scope, Discord never let it register slash commands in your server. The bot is online, it can read messages, but the / menu shows nothing from it.

2. The bot or its members lack the right permission. Even when commands are registered, a role needs the Use Application Commands permission to see and run them. If you have locked this down per-channel or per-role, members get a blank menu or a silent failure.

3. The bot can't respond in time. Discord gives a bot a strict 3-second window to acknowledge any interaction. If the bot is offline, its hosting server is down, or it crashed, it never replies, and Discord shows "This interaction failed." The command exists, it just got no answer.

Most of the time, fixing one of these three resolves the problem completely. Let's go through each.

Step 1: Re-invite the bot with the applications.commands scope

This is the first thing to try because it fixes the most cases.

When you generate an invite link in the Discord Developer Portal (or use a bot's official "Add to Server" button), the link contains a list of scopes. For slash commands to ever appear, that link must include applications.commands. Older links and some copied-around invites only request the bot scope, which is why a perfectly healthy bot shows zero commands.

To fix it:

1. Find the bot's official invite link. Use the one from the bot's own website or dashboard, not a random link someone pasted in a chat. Official links almost always include the correct scopes.
2. Open the link and select your server from the dropdown.
3. On the authorization screen, make sure the bot is being added with both bot and applications.commands access. You do not need to remove the bot first; re-authorizing on top of an existing install just adds the missing scope.
4. Approve it.

Within a minute or two, type / in any channel and the bot's commands should populate. If you want a full walkthrough of inviting a bot cleanly, see our step-by-step guide to adding a Discord bot.

A quick note: re-inviting does not kick the bot, reset its settings, or remove its roles. It is safe to do at any time.

Step 2: Grant the Use Application Commands permission to the right roles

If the commands still don't show, or only some members can see them, the problem is permissions.

Discord has a specific permission called Use Application Commands. By default it is granted to @everyone, but server owners often tighten permissions over time and accidentally remove it, either server-wide or in specific channels.

Check it in two places:

Server-wide: Go to Server Settings → Roles, pick the role in question (start with @everyone), and confirm Use Application Commands is enabled. If it's off, members of that role won't see slash commands anywhere.

Per-channel: Open the channel, go to Edit Channel → Permissions, select the role, and check that Use Application Commands isn't set to a red X. A channel-level override beats the server-wide setting, so a single bad override can hide commands in just one channel while they work everywhere else.

Also confirm the bot's own role has the permissions it needs to actually do the thing each command performs (kicking, sending messages, managing roles, and so on). A command can appear and even fire, then fail mid-action because the bot lacks the underlying permission. Our guide on what permissions to give a Discord bot breaks down which ones matter and why "Administrator" is rarely the right answer.

Step 3: Force a client cache reload so new commands appear

Sometimes everything is configured correctly and commands still don't show, especially right after a bot updates or you just re-invited it. This is a Discord client caching issue, not a server problem.

Your Discord app caches the list of available commands. New or changed commands can take a moment to sync, and the desktop or mobile client occasionally holds onto a stale list. Force a refresh:

• Desktop: Press Ctrl + R (Cmd + R on Mac) to reload the client. If that doesn't do it, fully quit Discord from the system tray and reopen it.
• Browser: Hard-refresh the page with Ctrl + Shift + R.
• Mobile: Swipe the app closed and reopen it, or pull down to refresh in a channel.

After the reload, type / again. Newly registered commands should now appear. If they appear after a reload, the underlying registration was fine all along, it was just a cache lag.

Why "This interaction failed" shows up even when commands exist

This error is different from missing commands. Here, the command shows up fine, you click it, and a few seconds later you get a red "This interaction failed." That means Discord delivered your click to the bot but never got a valid response within its 3-second deadline.

The usual culprits, in order of likelihood:

• The bot is offline. Check the member list. If the bot shows as offline or doesn't appear, it can't respond. This is by far the most common cause.
• The bot's host is down or restarting. Self-hosted and smaller bots go down when their server, VPS, or home machine restarts or loses connection. The command still exists in Discord's records, but nothing is listening.
• The bot crashed or is overloaded. During an outage or a traffic spike, a bot can be technically online but too busy to answer in time.
• A failed deploy. If a bot updated and the new version broke, commands registered before the crash will still be visible but won't respond.

What to do: confirm the bot is actually online, check the bot's status page or support server for a known outage, and try again in a minute. If a specific command fails every time while others work, that one command likely has a bug on the bot's side, report it to the bot's developers. For a broader checklist when a bot seems dead, see why your Discord bot isn't working and how to fix it.

The key takeaway: "interaction failed" is almost never your server's fault. It's the bot not answering.

Global vs guild commands and the registration delay

Here's a detail that trips up a lot of people and explains "I added the bot but commands took forever to show."

Bots register slash commands in one of two ways:

• Guild (server) commands register to a single server and appear almost instantly, usually within seconds.
• Global commands register across every server the bot is in. Discord caches these aggressively, and they can take up to an hour to fully propagate to all clients.

So if you just invited a bot that uses global commands, a short wait is normal. Reloading your client (Step 3) often pulls them in sooner, but if it's a brand-new global registration, patience is sometimes the actual fix. Well-built bots use guild commands for instant availability or register both, so most quality bots show their commands right away.

If commands never show after an hour and a client reload, go back to Step 1 (scope) and Step 2 (permissions), the delay isn't your problem.

How to avoid the problem entirely: bots that auto-register on invite

The cleanest fix is not having the problem in the first place. The difference between a bot that "just works" and one that makes you troubleshoot scopes is almost entirely down to how the bot is built.

Good bots:

• Ship an invite link that always includes applications.commands, so you can't accidentally add them without it.
• Use guild command registration so commands appear the moment the bot joins, no hour-long wait.
• Stay online reliably on real hosting, so "interaction failed" is rare.

PeakBot is built this way. Its official invite includes the right scopes by default, its commands register to your server immediately on join, and it runs on hosted infrastructure rather than someone's home PC, so you avoid the offline-bot version of "interaction failed." It's a free, AI-powered bot already powering 500+ Discord communities, and it replaces MEE6, Carl-bot, Dyno, and TidyCord with one tool, which also means one bot to keep online instead of four.

PeakBot includes 30+ free features with no time limit and no trial: AI moderation, XP and leveling, a ticket system, welcome messages, reaction roles, giveaways, polls, and full logging. Pro is $8.25/month per server (or $69/year) and adds the AI Server Builder, which builds an entire server, channels, roles, categories, and permissions, from a plain-English description in under 60 seconds. For comparison, MEE6 premium is $11.95/month and Carl-bot premium is $7.99/month, though Carl-bot remains a strong choice if reaction roles are all you need, and Dyno's $4.99/month tier is a budget-friendly option for basic moderation.

You can browse the full free feature list before deciding.

Frequently asked questions

Why are my Discord slash commands not showing up at all?

The most common reason is that the bot was invited without the applications.commands scope, so Discord never let it register commands. Re-invite the bot using its official link (which includes that scope), then reload your Discord client. If they still don't appear, check that the Use Application Commands permission is enabled for your roles.

What does "This interaction failed" actually mean?

It means Discord delivered your command click to the bot, but the bot didn't respond within the required 3-second window. Almost always the bot is offline, its host is down, or it crashed. Check that the bot shows as online in your member list and try again in a minute.

Why do new slash commands take a while to appear?

Bots that register global commands can take up to an hour to propagate across Discord because of caching, while guild commands appear in seconds. Reloading your client (Ctrl + R) often speeds it up. If commands never show after an hour, the problem is scope or permissions, not the delay.

Does re-inviting a bot reset its settings?

No. Re-authorizing a bot that's already in your server just adds any missing scopes, like applications.commands. It doesn't kick the bot, wipe its configuration, or remove its roles, so it's safe to do whenever commands stop appearing.

Do I need to give the bot Administrator permission to fix this?

No, and you shouldn't. Slash command visibility needs the Use Application Commands permission, and each command needs only the specific permission its action requires. Granting Administrator is a security risk; see our Discord bot permissions guide for the safe minimum.