Diagnostic Commands
Two commands let you check that the bot is set up correctly and working in your server. /health is a quick summary for support staff. /debug is a full report for administrators, with a section dropdown and a copy button for support tickets.
Both commands reply privately (only you can see the response).
/health
/health- Quick status at a glance
- Permissions, setup, role hierarchy
- Database, Redis, and gateway latency
/debug
/debug- Full report split into sections
- Per-channel permission breakdown
- Copy report button for support
/health
A fast health check for the current server.
/health
Permissions: Support staff or Administrator
It shows an overall status (Healthy, Degraded, or Critical) plus:
- Permissions: whether the bot has the permissions it needs
- Setup: how many categories and panels are configured and live
- Role hierarchy: whether the bot can assign your automation roles
- Connectivity: database, Redis, and gateway response times
- Plan and usage: current tier, open ticket count, and uptime
The reply is only visible to you. Run /debug for the full breakdown.
/debug
A detailed diagnostic report for administrators.
/debug
Permissions: Administrator
The report opens on an overview and includes a dropdown to switch between sections, plus a Copy report button that produces a plain-text summary you can paste into a support request.
Sections
| Section | What it covers |
|---|---|
| Overview | Overall status and a summary of any issues |
| Permissions | Server-wide bot permissions, plus per-category and per-panel channels |
| Roles & Hierarchy | The bot's highest role and whether it can assign your automation roles |
| Server & User | Server details and your own account and access |
| Plan & Usage | Current tier, limits, feature flags, AI usage, and open tickets |
| Connectivity | Database, Redis, and gateway status, plus the bot user and app IDs |
Role hierarchy
A common silent failure is the bot having the Manage Roles permission while
its own role sits below a role it tries to add or remove. /debug flags this
under Roles & Hierarchy. Fix it by dragging the bot's role above the affected
roles in Server Settings, Roles.
Reading the status
Both commands report one of three states:
| Status | Meaning |
|---|---|
| Healthy | No issues found |
| Degraded | Tickets still work, but something needs attention |
| Critical | A core problem (for example, missing permissions or database down) |