Troubleshooting

Agent Offline in Discord?

A focused recovery checklist when your agent suddenly stops replying, appears offline, or works in one place but not another.

This is one of the highest-friction problems in community support: "it worked yesterday, now it looks offline." In most cases, the fix is permission scope, channel setup, or a stale client state — not a full rebuild.

Fast truth: start with channel-level checks before assuming your container or account is broken.

What “offline” can actually mean

The bot is online, but blocked by channel-level permissions.
Slash commands are restricted in Discord Integrations settings.
You are testing in a different server/channel than expected.
Discord client cache is stale (especially after role changes).
There is a real backend issue (less common, but possible).

5-minute recovery flow

1) Run a minimal @mention test

In the exact channel where you expect it to work, send:

@YourAgent reply with exactly: ONLINE TEST OK

If this fails, continue below. If it succeeds, your issue is likely prompt size or workflow-specific.

2) Verify channel permission overrides

For the bot role in that channel, confirm:

View Channel = allowed
Send Messages = allowed
Read Message History = allowed
Use Application Commands = allowed

Channel overrides can block a bot even when server-level permissions look correct.

3) Check Discord Integrations restrictions

Go to Server Settings → Integrations and confirm the app is allowed in the channel/role scope you are testing.

4) Refresh Discord client state

Desktop: hard refresh Discord client. Mobile: fully close/reopen app. Then run the same minimal @mention test again.

5) Isolate platform vs backend

Try a prompt from the Heyron dashboard. If dashboard works but Discord does not, treat it as Discord scope/permissions. If both fail, escalate as backend/system issue.

Common false assumptions

“Bot shows offline so backend is down.” Presence can lag; always test with a minimal mention.
“It has Admin role, so permissions are fine.” Channel overrides can still deny interaction.
“Slash commands are missing, so the app is broken.” Often caused by Integrations restrictions or stale client cache.

Escalation packet for #help

If it still fails after the checklist, paste this (short and structured):

Issue: Agent appears offline / not replying in Discord Server + channel: [name] What changed recently: [roles, channels, reconnect, none] Minimal test used: @Agent ONLINE TEST OK Result: [no response / delayed / error] Dashboard test result: [works / fails] Checks completed: [permissions, integrations, client refresh] Approx time + timezone: [e.g., 4:20 PM ET]

Tip: Run one clean test, then wait. Sending repeated pings in multiple channels makes diagnosis harder.

Bottom line: most "offline" reports are recoverable in minutes with channel permissions + integrations checks. Treat backend failure as the last diagnosis, not the first.