Troubleshooting
Common logging problems and fixes.
| Problem | Likely cause | Fix |
|---|---|---|
| No logs at all | channelId is null, the LogConfig row is missing, or toggles are off. | Choose a Log Channel and enable at least one event in /dashboard/<guildId>/logging. |
| Logs still use old settings | The bot has cached the old LogConfig for up to 5 minutes. | Wait for the cache to expire, then trigger a new event. |
| Message edit did not log | The text content did not change, such as a link preview/embed update. | This is expected; only content changes are logged. |
| Deleted content says no text or unknown | Discord did not provide content or the old message was partial/uncached. | Enable the required Discord intents/cache behavior for your deployment and understand that old content may not always be available. |
| Voice mute/deafen was not logged | The module ignores voice state updates where the channel did not change. | Only join, leave, and move events are logged. |
| Webhook was saved but logs still appear from the bot user | The config is cached for 5 minutes; or the webhook URL was rejected (only discord.com/api/webhooks/… forms are accepted). | Wait a few minutes or toggle any switch to refresh the cache; re-paste the URL from Channel settings → Integrations → Webhooks. |
| Logs stopped after I deleted the webhook in Discord | The bot detected the dead webhook and fell back to the log channel. | Nothing to fix — optionally remove the stale webhook on the Logging page. |
| Channel save fails | The selected channel does not belong to this server. | Pick a channel from the same guild. |
Private information
Message delete and edit logs can include user-written content. Put the log channel somewhere only trusted staff can read.