WilBot does not respond
Check that it is online, that its role can View Channel and Send Messages, and that you mentioned it or used a slash command in a channel it can access.
Open related guideStart with the closest symptom below. Each answer links to the longer guide where one exists.
Check that it is online, that its role can View Channel and Send Messages, and that you mentioned it or used a slash command in a channel it can access.
Open related guideDiscord caches command registration. Check the server has the current install, wait briefly after a restart, and confirm the bot role can use application commands.
Open related guideStart with a web-only conversation, then check that you are signed in with the same Discord account and that the local Discord bridge is online.
Open related guideCheck your remaining creator units, simplify the prompt, and try again once. Provider outages are shown on the status page; do not spam retries.
Open related guideConfirm WilBot can view and send in the welcome channel, then check the server's welcome configuration and audit logs.
Open related guideMove the server to review or monitor mode, inspect the evidence, and use the staff feedback controls before enabling automatic action again.
Open related guideWilBot needs View Audit Log. Ask for the member's nickname history and compare the returned actor and timestamp with Discord's audit log.
Open related guideChoose a longer lookback window and confirm WilBot has been present long enough to collect data. Private message content is not required for aggregate charts.
Open related guideCheck live service health, then contact support with the server ID, approximate time, command used, and the error text. Never include a bot token or API key.