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

Discord check-in shows only titles or empty message body

Discord check-in shows only titles or empty message body

The compiled check-in lands in your Discord channel, but you only see headings (for example participant names or question titles) with no answer text, or the message looks empty except for a title line. Slack or the web dashboard may show full responses while Discord does not.

Quick check

  • Report destination — In the check-in settings, confirm the Report / Summary channel is the Discord channel where you are looking (not a Slack channel left over from a migration).
  • Bot in channel@Dailybot must be a member of that channel with permission to Send Messages and Embed Links.
  • Responses exist — Open the same check-in date on the web under Check-ins and verify participants actually submitted answers (not only opened the reminder).
  • One Dailybot app — Remove duplicate Dailybot bot invites on the server; multiple installs can register conflicting behavior.
  • Re-select channel — Clear the report destination, save, and pick the Discord channel again from the picker so the stored channel ID refreshes.

Common causes and fixes

Report destination still points to another platform

Teams that moved from Slack to Discord sometimes leave the old Slack channel as the compile target. The web UI may still show a label while posts go elsewhere (or fail partially). Set the destination to the intended Discord text channel and run a test compile after at least one participant responds.

Discord summaries often use embeds. If Embed Links is denied for the bot role in that channel, clients may render a stripped message (titles without body). In Channel Settings → Permissions, allow Send Messages, Embed Links, and Read Message History for the Dailybot role. Compare with a public channel test: temporarily post the report to a channel with simple permissions to isolate overrides.

Channel is private or thread-only without the bot

Private channels and some thread setups require an explicit /invite for the bot. If the bot is not in the thread where you expect the summary, you might see partial UI from other integrations or old messages. Invite the bot, then re-run or wait for the next scheduled compile.

Stale channel after rename or delete

Renaming or recreating a Discord channel changes its ID. The check-in may still reference the old ID. Re-pick the channel in Report destination and save. See also Channel name looks stale.

All participants skipped or empty answers

If nobody answered required questions, the compile can post structure with little or no body. Confirm on the web that answers exist for that date. If one member is empty, see A member’s reports aren’t appearing.

Broader Discord command or interaction issues

If slash commands and reminders also broke at the same time, fix the shared Discord pipeline first: Slash commands aren’t working in Discord and Function calling in Discord.

If none of this worked

Before contacting support, collect:

  • Discord server name (or ID if you can share it) and exact channel name
  • Check-in name and screenshot of Report destination settings
  • Screenshot of the broken Discord message and the same date on the web check-in view
  • Whether the problem is every day or started after a permission, migration, or bot re-invite change
  • Whether Reports not posting describes a different symptom (no message at all)

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

Want to go deeper? See the Dailybot Academy for async standups on chat platforms.