Docs Navigation
Assistance

Troubleshooting

Start here when Monitor is installed but something is not behaving as expected.

Monitor says the bot is not found

Why: The selected bot is not a member of the server or was not selected correctly.

Fix: Invite the target bot and run /monitorsetup or /monitorconfig again.

Monitor cannot send to the channel

Why: Monitor is missing View Channel, Send Messages, or Embed Links.

Fix: Grant those permissions or choose another notification channel.

No offline alert appeared

Why: The bot recovered during the grace period or monitoring is disabled.

Fix: Check /monitorstatus and verify the bot stayed offline long enough to cross the grace period.

No role mention appeared

Why: The role is managed, above Monitor's top role, or otherwise not pingable.

Fix: Choose a role Monitor can safely mention and check the Monitor role position.

Dashboard does not show a new channel or role

Why: The page may still have cached Discord resources.

Fix: Use the dashboard's manual resource refresh control.

Heartbeat is UNKNOWN

Why: A heartbeat token exists but Monitor has not received a heartbeat.

Fix: Follow the Heartbeat Telemetry integration guide and verify the bot is sending requests.

Heartbeat is ZOMBIE while Discord says Online

Why: Application-level heartbeat telemetry stopped arriving.

Fix: Check the heartbeat task, event loop, and outbound HTTP connectivity in the monitored bot.

Developer help

For heartbeat payloads, API authentication, shard telemetry, and integration errors, use the developer documentation section.

What can make a bot look offline?

Discord does not expose the exact crash reason to Monitor. A bot can disappear because of a process crash or exception, a deployment or host restart, a network or gateway disconnect, an invalid/revoked bot token, a shard disconnect, or a Discord-side incident. Monitor therefore reports the observable fact — Discord says the bot is offline — rather than inventing a cause.

Heartbeat Telemetry adds application-level evidence. LATE means heartbeats are delayed, while ZOMBIE means they have exceeded 2.5× the expected interval. A zombie heartbeat is telemetry only and does not trigger outage pings or alter uptime/downtime records.