The short answer
Identify the failed stage first. Missing commands call for installation and command-access checks; explicit errors call for their exact requirements; broad silence calls for usage/provider-status checks. Compare the same person in another permitted channel, then another ordinary member in the original channel.
Different symptom or still not fixed? Find the next check →Key facts
- Record the stage
- No candidate, execution error, no reply or success
- Harmless comparison
- Use the provider’s documented read-only/help operation; do not assume /help exists
- Separate permissions
- A user invoking a command and a bot performing an action are different checks
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| The bot/command is absent after typing / | Inspect invocation method and installation scope. | Step 1 |
| Command appears but reports permission/input errors | Read whether the failure concerns the user, bot or supplied options. | Step 3 |
| The application did not respond | Compare another permitted channel and ordinary member. | Step 2 |
| You can use it in another channel | Inspect the original channel and bot-specific allowed locations. | Step 4 |
| Another ordinary member succeeds in the same channel | Inspect your roles, overrides or app-specific account conditions. | Step 4 |
| Only this bot fails for every tested person/location | Inspect provider status, usage changes and reply destination. | Step 5 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1｜For missing commands, inspect usage and installation scope
A command appearing and the app responding are different stages.
Time: Compare one change at a time
- Type / in the affected channel and identify both the command and its provider. Several apps can expose the same command name.
- If you used a legacy prefix such as !, inspect the app profile or directory page for its current invocation method. Command names and prefixes are not universal.
- An administrator can inspect Server Settings → Integrations for server-installed apps. Distinguish those from your account-added apps under User Settings → Authorized Apps.
- If installed but absent from the picker, continue to Step 2. If not installed in the intended scope, use the add-app guide. Do not repeatedly remove/re-add without checking.
Results that did not fix the problem help the next reader too.
Step 2｜Change channel and user separately using the same command
Use only an allowed location and a documented operation that does not alter settings or delete, ban or notify people in bulk.
Time: Compare one change at a time
- Try once as yourself in the original channel, keeping options fixed. Record no candidate, exact error, no reply or success. Do not repeatedly submit while a response is delayed.
- Try the same operation yourself in another permitted text channel in the same server. Success only there points to the original channel’s conditions in Step 4.
- Ask another willing ordinary member to make the same comparison in the original channel using their own account. If only they succeed, inspect user roles/overrides or provider account requirements; never borrow their login.
- Success only for an administrator does not establish ordinary-member access. Owners/administrators can access commands despite restrictions affecting other members; record that role difference.
- If every tested user/channel fails, continue to Step 5. If only your desktop app omits the candidate, compare the same account/channel in the browser and reload the app.
Examples describe how to interpret your own results: success in B but failure in A prioritizes A; another ordinary member succeeding in A prioritizes user-specific conditions. Unperformed comparisons remain unconfirmed.
Results that did not fix the problem help the next reader too.
Step 3｜Use the exact execution error to choose the next check
Separate app-specific explanations from a Discord response failure after submitting a command.
Time: Compare one change at a time
- For missing/invalid options, follow the command picker’s documented types and required selections. Identify the specific date, URL, user or other input requested.
- For permission errors, identify whether the user lacks invocation access or the bot lacks authority for its action. If unclear, give the full error to the administrator instead of increasing privileges by guesswork.
- For provider-specific cooldowns, limits or incomplete account linking, follow its guidance. There is no universal waiting period for every bot.
- The application did not respond means the required response was not obtained; it does not uniquely identify a permission failure. Use Step 2’s comparisons and provider status.
- Even if a reply appears, confirm the intended action completed where appropriate. For failed role assignment or another operation, compare feature-specific permissions and role hierarchy with the provider’s guidance.
Results that did not fix the problem help the next reader too.
Step 4｜Administrators: separate command access from bot actions
Record the existing settings and change only the scope narrowed by the comparison.
Time: Compare one change at a time
- For user-dependent candidate/execution access, inspect the affected person’s Use Application Commands permission under Server Settings → Roles.
- Inspect that channel’s role/member overrides and the app’s available command restrictions under Server Settings → Integrations, including allowed users/channels.
- If the bot cannot post or perform its action, inspect only the relevant permissions in that channel, such as View Channel and Send Messages. History, attachments or role management are relevant only when the actual feature requires them.
- Interaction responses and ordinary message posts have different conditions. Send Messages is not a universal repair for every command. Inspect any provider-specific allowed-channel setting too.
- Have the originally affected ordinary member repeat the same command in the same channel. Verify the expected result as well as the candidate display, and restore unnecessary changes.
Users without settings access should pass comparison results to the administrator. Do not grant Administrator to the bot or user merely as a test.
Results that did not fix the problem help the next reader too.
Step 5｜For widespread silence, inspect the provider and reply destination
An online indicator does not prove every command works; a member-list state does not establish that every app feature has failed.
Time: Compare one change at a time
- Check the provider’s expected reply location: some results are visible only to the invoking user, in DMs or in a designated channel.
- Use the app profile/directory overview to find its support destination. Inspect incidents, maintenance and changed commands; note whether other functions still work.
- If several apps and normal Discord operations fail, check Discord Status too. For a reported bot-specific incident, pause PC reinstalls and server changes until recovery.
- If unresolved, send the provider the bot/command/options, time, exact error and channel/user comparisons. Redact private screenshot details; never send bot tokens, passwords or authentication codes.
Results that did not fix the problem help the next reader too.
Avoid
- Do not use deletion, bans or bulk notifications as test commands.
- Do not spam retries, borrow another member’s account or grant blanket Administrator access.
Important cautions
- Keep the same command/options across comparisons and distinguish ordinary members from administrators.
- For support, explicitly record what was tested and what remains unconfirmed, including whether another command still works.
FAQ
The bot is online but does not reply.
Online status does not verify each command or its external dependencies. Compare the same operation across a channel and ordinary user, then inspect provider status.
Administrators can use it, but ordinary members cannot.
Inspect member roles, channel overrides and Integrations command restrictions. Retest as the original affected member, since an administrator’s success is not an equivalent permission check.
Does The application did not respond mean missing permissions?
Not by itself. Response delay/failure can also produce it. Record the message and comparisons without flooding repeated requests.
An app is absent from Members, but its commands appear.
It may be added to your account rather than the server. Inspect Authorized Apps and the intended installation scope.
Is kicking and re-adding faster?
First inspect scope, permissions and provider health. Re-adding cannot guarantee recovery from a provider outage, and retained settings differ by app. Use that route only when justified by its guidance.
Sources
English adaptation of the existing Japanese article. Official documentation supports the described controls and limits; comparison sequences are editorial guidance rather than measured results. Follow the permissions of the actual device, account and server, record original settings and verify the outcome before making another change.
Discord: using, adding and removing appsDiscord developer documentation: permissions and role hierarchyDiscord: channel permissionsDiscord: command restrictions and administrator accessDiscord developer documentation: interaction responsesDiscord Status: service incidentsDiscordJapanese version of this page