Stoatmod / Troubleshooting hub

Troubleshoot Stoatmod

Start with the real server state, then work backward through command syntax, permissions, hierarchy, channel access and the case or event record.

All documentation

The details, in one place.

Diagnose Stoatmod commands that do not respond, permission failures, role hierarchy and mismatched success records.

  • Reviewed 31 August 2026
  • 3 sections
  • Documentation

Fast diagnostic order

  1. 01

    Confirm the command syntax

    Toggle commands use enable, disable or status.

  2. 02

    Run setup

    Collect missing permissions and hierarchy findings.

    ~setup
  3. 03

    Check the channel

    Make sure the bot can view, read and respond in the exact channel.

  4. 04

    Inspect the target

    Confirm the member or role is below Stoatmod.

  5. 05

    Compare response and reality

    Check whether the message, timeout, ban or role actually changed.

Common causes

  • The bot role is below the member or automatic role.
  • A channel override denies a required permission.
  • The wrong command form was used.
  • A provider or network failure triggered fail-open behaviour.
  • A dashboard setting and legacy command are using different policy paths.
  • The displayed audit record came from an older deployed bot version.

Prepare a useful support report

  • Server ID, channel ID and affected user or role ID.
  • Exact command without private tokens.
  • Time in UTC.
  • Expected and observed real server state.
  • Relevant case or audit reference.
  • Screenshots with personal information removed where possible.

Continue the task

Related Stoatmod resources

Fix role hierarchy failuresOpen resource →Fix commands that do not respondOpen resource →Service statusOpen resource →

Ready to configure a server?

Install Stoatmod, then verify the first outcome.

Open the official bot profile →