Troubleshooting
Diagnose command, dashboard, permission, music, and automation problems methodically.
The first five checks
- Check the public status page for a known incident.
- Confirm Airwavy is still installed and can see the affected channel.
- Reload the dashboard and verify the saved server and feature values.
- Check Discord role hierarchy and channel overwrites.
- Reproduce once with a normal member account and record the exact time, server, channel, command, and visible error.
Commands do not appear or run
A slash command is missing
Confirm you selected the Airwavy application in Discord's command picker and that application commands are allowed in the server or channel.
Missing Permissions
Open the command's reference entry, grant only its declared bot permissions, then check target role hierarchy and channel overwrites.
You are on cooldown
Wait for the command's listed cooldown before retrying. Repeated retries do not make a permission or service error succeed.
Music and voice
No audio
Check Connect, Speak, server mute/deafen, and the channel user limit. Try another supported source after permissions are confirmed.
The bot leaves an empty channel
After the configured grace period Airwavy clears playback. Non-24/7 players disconnect; premium 24/7 players remain connected and ready for a future /play.
The bot stays connected but is silent
That is expected after an empty-channel cleanup in 24/7 mode. Add a new track with /play; the player should not remain stuck paused.
Dashboard
A server is absent
Confirm the bot is installed and your Discord account currently has the required server management authority, then sign in again.
A save fails
Fix validation errors, check service status, and retry the same small change. Do not repeatedly submit conflicting edits from multiple tabs.
Bot response and rate limits
The bot does not respond
Check service status, confirm Airwavy can view and send in the channel, wait for any command cooldown, then retry once. Record the exact command, time, and visible request or error code.
You are being rate limited
Stop retrying, wait for the displayed cooldown or retry period, and reduce repeated commands or image requests. If many users are affected, check service status.
A temporary outage is reported
Do not repeatedly submit the same action. Preserve the error or request code, wait for recovery, and verify the final state before trying again.
Images
An image or card does not render
Try the default background, verify the source is a supported PNG, JPEG, GIF, or WebP image within the published limits, and remove expiring or access-controlled URLs.
AI image generation fails
Shorten the prompt, remove unsafe content, wait after a rate-limit response, and retry after provider or service availability recovers. Never put secrets or private member data in a prompt.
Browser, authentication, and mobile
Sign-in loops or expires
Allow the required site cookies, verify the device clock, close duplicate sign-in tabs, then sign out and begin again from the official dashboard.
The dashboard behaves differently after an update
Reload the page without an old tab, then retry in a supported current browser. Do not clear site data until you have recorded unsaved changes and the visible error.
Mobile navigation does not open or close
Reload once, check browser zoom and orientation, then try the menu and close controls. Report the device, browser version, orientation, and exact route if it continues.