Troubleshooting

Discord Bot Typing... Then Nothing?

Fix the high-friction case where your agent shows the typing indicator but never sends a message.

This issue is common in #help and #tips-and-tricks: the bot appears alive, starts typing, and then stops with no visible reply. Usually this is a channel-policy mismatch, response-policy rule, or a blocked send path—not a "dead model."

Core rule: typing indicator means the bot saw your message. The failure is usually on the send/permission/policy side.

2-minute isolation flow

Create a fresh test channel with minimal restrictions.
Give the bot role explicit View Channel + Send Messages + Read Message History.
Temporarily disable complex moderation/auto-delete bots in that channel.
Send a plain message: @bot reply with exactly "pong".
If that works, your original channel has policy/override issues.

Most common causes

Channel override conflict: role can read but cannot send in this specific channel/thread/forum post.
Discord Integrations command restrictions: slash/mention handling is limited by server integration settings.
Mention policy mismatch: bot is configured to require mentions, but users send plain text (or vice versa).
Group policy closed: DM works, server channels stay silent until group policy is opened.
No restart after config edits: changes made, but runtime still using old settings.

Known-good recovery sequence

1) Confirm these settings in agent config: - requireMention: false (or keep true, but always @mention during test) - groupPolicy: open 2) Save config, then restart gateway/runtime. 3) Run this test in a clean channel: @YourBot reply with exactly: pong 4) If still typing-then-silent, test in DM. - DM works + channel fails = channel/integration permission issue - DM fails too = broader runtime/config issue

Important: one successful DM does not prove channel setup is correct. DM and server channels are different permission surfaces.

When the issue is thread/forum specific

Ensure the bot can Send Messages in Threads.
If using forum channels, test in a normal text channel first.
Check category-level permission sync; unsynced child channels can silently override role grants.

Copy/paste support packet

Discord typing-then-silent report Server ID: Channel ID (failing): Channel type (text/thread/forum): Bot permissions in failing channel: Works in DM? (yes/no): Works in clean test channel? (yes/no): requireMention value: groupPolicy value: Did you restart after config changes? (yes/no): Exact test message used: Observed behavior (including typing duration):

Bottom line: this is usually a permission/policy mismatch, not model failure. Use a clean channel + explicit ping test to isolate quickly and stop guessing.