Skip to content
Tutorials

Bot Status Use Cases

Use Bot Status to understand bot/web status, Discord reachability, notification delivery, OCR runtime, RaidHelper, tickets, and recent problems.

Data and Status
Who uses it
Managers, super admins, support-minded staff
Where it lives
Dashboard > Operations
Goal
Staff can separate real incidents from normal noise and send maintenance messages when needed.
On This Page5 sections

Before You Start

  • Operations or manager-level dashboard access.
  • Configured channels and modules you want to monitor.

Steps

  1. Check process and service health

    Start with bot and web heartbeat status. A stale heartbeat means the process may be down or not publishing health data.

  2. Review Discord reachability

    Use channel and role checks to spot permission or deletion problems. If a configured destination is unreachable, fix Discord permissions or update GearCheck settings.

  3. Fix what needs attention, then read Recent problems

    Needs attention ranks what to fix first, critical before warning, each card with its own fix. Recent problems groups failures from the latest 250 audit events, up to 8 kinds, and Open in Audit Log shows each event. A notice that reached every channel is not a problem.

  4. Post a notice, checked before it goes out

    Post a notice opens a panel: the type, a title, the message and the channels it is for. The preview shows exactly what posts. Review and post opens a confirm naming the server, every channel and the exact words; nobody is pinged, and GearCheck can't take a posted notice back. If a channel fails, the panel says why, and Retry posts the same notice to that channel only.

Check It Worked

  • Warnings map to a specific action.
  • Configured channels still exist and are reachable.
  • Recent problems are real failures, each one open in the Audit Log.
  • Maintenance notices were sent only to intended destinations.

Common Pitfalls

  • Treating every warning as an outage.
  • Posting again after GearCheck didn't answer. The notice may have posted: check the channels or the Audit Log first.
  • Ignoring stale configured channels after Discord cleanup.