Troubleshooting
Common failure modes and the fixes grounded in the current implementation.
If nothing happens when members post, first confirm suggestChannelId is set on /dashboard/<guildId>/suggestions and that you are testing in exactly that channel. The bot keeps a 30-second cache of suggestion settings, so very recent dashboard changes may not be visible immediately.
| Problem | Likely cause | Fix |
|---|---|---|
| Original message stays and no card appears | No suggestion channel is configured, the message is in the wrong channel, or the author is a bot. | Set the channel in the dashboard and test with a normal member account. |
| Original disappears but no thread appears | suggestionAutoThread is off, or the bot lacks thread permissions. | Enable auto-threading and grant Create Public Threads. Thread creation failures are logged but do not stop the card. |
Vote says Suggestion not found | The card points to a suggestion ID that no longer exists in the database. | Do not reuse old copied buttons; recreate the suggestion or restore the row. |
| Emoji save fails | The API rejected a non-string or overlong emoji value. | Use an emoji or custom emoji mention no longer than 64 characters. Empty values reset to defaults. |
| Dashboard list is stale | The initial list is server-rendered and live updates only arrive after stream events. | Refresh the page for old changes; new votes should update through SSE when the stream is connected. |
| Missing cards after posting image only | The attachment was not detected as an image, or the message had no image and no text. | Use an attachment whose content type starts with image/, or include text. |
Role hierarchy does not control votes
Votes are open to users who can press the buttons. The current vote handler does not check staffRoleId, member permissions, or author identity.