> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bloombot.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Commands not responding

> What to check when Bloom stays silent, replies that you are going too fast, or runs something you did not expect.

Bloom stays silent on names it does not recognize, so a command that does nothing usually means it was never recognized in the first place.

## Bloom says nothing at all

<Steps>
  <Step title="Confirm the prefix">
    Send `b.help`, which works no matter what the server's prefix is, or mention Bloom directly. Both bypass the prefix entirely and tell you what is set.
  </Step>

  <Step title="Check Bloom can see the channel">
    Bloom needs View Channel, Send Messages, and usually Embed Links where you are typing. A channel override can deny these in one channel only.
  </Step>

  <Step title="Check the spelling">
    Unknown names produce no reply on purpose, so a typo looks the same as a broken bot. Run `!help <command>` to confirm the name.
  </Step>

  <Step title="Check whether the command is restricted">
    A server can disable or restrict commands by channel or role. If it works elsewhere but not here, that is the likely reason.
  </Step>
</Steps>

## Other symptoms

<AccordionGroup>
  <Accordion title="Bloom says I am using commands too quickly">
    You have run commands faster than Bloom accepts them. The limits are per user and clear on their own, so wait a moment and try again. Bloom mentions this occasionally rather than on every blocked message.
  </Accordion>

  <Accordion title="A command works for me but not for a moderator">
    That is a permission or hierarchy difference, not a broken command. See [Permission errors](/troubleshooting/permissions).
  </Accordion>

  <Accordion title="My alias runs something unexpected">
    Real command names are matched before your aliases, so an alias that collides with a built-in name never fires. Run `!aliases` to see what is taken.
  </Accordion>

  <Accordion title="Commands do nothing in direct messages">
    Bloom's prefix commands are server commands. In direct messages it responds only to verification flows, such as a [join gate](/security/join-gate) captcha. Run commands inside a server.
  </Accordion>

  <Accordion title="A command replies with its usage instead of running">
    A required argument is missing or in the wrong position. The usage line shows `<required>` and `[optional]` parts in the order Bloom expects them.
  </Accordion>
</AccordionGroup>

## Related pages

<CardGroup cols={2}>
  <Card title="Using prefix commands" icon="terminal" href="/getting-started/commands">
    How Bloom reads what you type.
  </Card>

  <Card title="Permission errors" icon="circle-question" href="/troubleshooting/permissions">
    When a command is refused rather than ignored.
  </Card>

  <Card title="Command aliases" icon="wand-magic-sparkles" href="/configuration/aliases">
    Creating and inspecting your own shortcuts.
  </Card>

  <Card title="Support server" icon="discord" href="https://discord.gg/HYSgTQ6SHR">
    Ask if a command still will not run.
  </Card>
</CardGroup>