Skip to content
New Dailybot 3 is live. Read the launch
Troubleshooting Discord Admin team-manager Member

Discord troubleshooting: what to check when Dailybot misbehaves on Discord

Discord troubleshooting: what to check when Dailybot misbehaves on Discord

Use this as a hub for Discord-specific problems. Pick the section that matches what you see.

Pick your symptom

What’s happening Go here
Check-in posts only titles or empty body Empty check-in messages
Bot does not reply to any slash command Function calling on Discord
Channel summaries never arrive in Discord Reports not posting
Kudos misbehaves on Discord Kudos not working in Discord
Bot disappeared from your server Bot not appearing
Need to reinstall Dailybot on Discord Disconnect and reconnect

If you do not find your case below, this overview gives the diagnostic ladder.

Quick health check (1 minute)

  1. Open your Discord server.
  2. Type /dailybot in any text channel. You should see Discord auto-complete the bot’s commands.
  3. If the autocomplete is empty, the bot is not present or not registered for that server – continue with reinstall.
  4. If autocomplete works but /dailybot help returns nothing, the bot is present but not responding – continue with function calling.
  5. If commands work but check-in messages are broken, jump to empty messages.

Common Discord-only causes

1. Permissions per channel

Discord’s permission model is per-channel and per-role. Even if the bot has Send Messages server-wide, a specific channel can deny it. Check Channel Settings -> Permissions for the Dailybot role and confirm:

  • View Channel
  • Send Messages
  • Embed Links (required for rich summaries)
  • Read Message History
  • Use Application Commands (slash commands need this)

2. The bot is in the server but not in the channel

A private channel or a thread may not include the bot. Right-click the channel -> Add member or role -> select the Dailybot role. Threads also require the bot to be invited explicitly.

3. The server has too many bots

Discord registers slash commands per-app. If a server is at the slash-command limit, new bots may fail to register. Remove unused bots or move some commands to a different server.

4. Bot was kicked and re-invited (new ID)

Re-inviting can change the bot’s role or scope. After a re-invite, re-pick channels in the check-in’s report destination so the stored ID matches the new install.

5. Discord-wide outage

When Discord itself has incidents (gateway, voice, or slash commands), Dailybot looks broken even though Dailybot is fine. Check discordstatus.com before deeper debugging.

6. Multiple Dailybot installs in the same server

If two Dailybot apps were installed at different times (e.g., before and after a workspace rename), they may conflict. Keep only one and re-authorize the active install.

What to send support if nothing works

If you have to escalate, please collect:

  • The Discord server name (or ID if you can share it).
  • The exact channel where the problem happens.
  • A screenshot of what you see and what you expected.
  • The output of /dailybot help (or “no autocomplete” if it does not appear).
  • Whether the problem affects everyone or only some members.
  • Whether other bots in the same server work as expected (rules out server-level issues).

Then contact Dailybot support from Help / Contact in the product or on the website.