Bot Not Responding to Commands
Prowl isn't responding to any slash commands
Prowl isn't responding to any slash commands
1
Check the status page
Visit status.prowlbot.xyz and confirm there are no active incidents affecting the bot. If there is an ongoing outage, wait for it to be resolved.
2
Verify Prowl is in your server
Go to your Discord Server Settings → Members and confirm Prowl appears in the member list and shows as online (green dot). If it’s offline, there may be a broader service disruption.
3
Check channel permissions
Prowl needs at minimum View Channel, Send Messages, Embed Links, and Use Application Commands in the channel where you’re typing. Open Channel Settings → Permissions, find the Prowl role, and confirm none of these are explicitly denied.
4
Confirm commands aren't restricted
Open the dashboard, navigate to your server, and check the command settings. A server admin may have limited a command to specific roles or channels.
5
Re-invite the bot if slash commands are missing
Discord occasionally loses slash-command registrations. If commands don’t appear at all, try removing Prowl and re-inviting it from prowlbot.xyz. Wait two to three minutes for Discord to propagate the new registration.
Commands work in some channels but not others
Commands work in some channels but not others
This is almost always a channel-level permission issue. Open the settings for the non-working channel, go to Permissions, and look for an explicit Deny on Send Messages or Use Application Commands for either the
@everyone role or the Prowl role. Remove the deny override or add an explicit Allow for Prowl.Missing Permissions Errors
Prowl says it's missing permissions when I run a command
Prowl says it's missing permissions when I run a command
1
Identify the required permission
The error message from Prowl will usually name the missing permission (e.g., “I need the Manage Roles permission to do this”). Note it down.
2
Check the Prowl role in Server Settings
Go to Server Settings → Roles, find the Prowl role, and verify the required permission is toggled on. If it’s off, enable it and save.
3
Check role hierarchy
Prowl can only manage roles and members that sit below its own role in the hierarchy. If you’re asking Prowl to assign a role that is ranked higher than the Prowl role, drag the Prowl role above it in Server Settings → Roles.
4
Reauthorize with correct permissions
If the Prowl role is missing many permissions, the bot may have been invited without the full permission set. Re-invite Prowl from prowlbot.xyz — Discord will prompt you to update its permissions.
Prowl can't create or manage channels/threads for tickets
Prowl can't create or manage channels/threads for tickets
Ticket creation requires Manage Channels, Send Messages in Threads, and Create Public/Private Threads permissions. Verify all three are granted to the Prowl role in Server Settings → Roles. Also confirm the category where tickets are created doesn’t have a Deny override for Prowl on any of these permissions.
Music Not Playing / Bot Won’t Join Voice
Prowl joins the voice channel but no audio plays
Prowl joins the voice channel but no audio plays
1
Check your own audio output
Make sure your Discord output device is set correctly and your volume isn’t muted. Other members in the channel should be able to confirm whether they can hear music.
2
Verify the source URL or query
Certain sources may have restrictions. Try a different song or use a direct search term (e.g., the song title and artist name) rather than a platform-specific URL.
3
Check the bot's voice permissions
Prowl needs Connect, Speak, and Use Voice Activity in the voice channel. Open Channel Settings → Permissions for the voice channel and confirm these are allowed.
4
Run /music stop and restart the queue
Run
/music stop to fully reset the music player, then start a fresh queue with /music play. A corrupted queue state can prevent audio from starting.Prowl won't join my voice channel at all
Prowl won't join my voice channel at all
Confirm that Prowl has the Connect permission in that specific voice channel. If the channel has a User Limit set, make sure it isn’t full. Also check that you are currently in the voice channel when you run the
/music play command — Prowl joins the channel you are in at the time of the request.Dashboard Not Loading or Login Issues
The dashboard at prowlbot.xyz won't load
The dashboard at prowlbot.xyz won't load
1
Check service status
Visit status.prowlbot.xyz and look for any dashboard-specific incidents.
2
Clear your browser cache
A stale cache can prevent the dashboard from loading correctly. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to hard-refresh.
3
Try a different browser or incognito mode
Browser extensions (particularly ad blockers and script blockers) can interfere with the dashboard. Open an incognito window to rule this out.
4
Check your internet connection
If other sites work normally, try accessing the dashboard from a mobile device on cellular data to determine whether the issue is network-specific.
I can't log in to the dashboard — Discord OAuth keeps failing
I can't log in to the dashboard — Discord OAuth keeps failing
1
Ensure cookies are enabled
The dashboard uses cookies to maintain your session. Verify that your browser allows cookies from
prowlbot.xyz.2
Revoke and re-authorize
In Discord, go to User Settings → Authorized Apps, find Prowl, and click Deauthorize. Then return to prowlbot.xyz and log in again to grant fresh OAuth permissions.
3
Check Discord's own status
If Discord’s OAuth service is degraded, login will fail regardless. Check discordstatus.com for any OAuth-related incidents.
AutoMod Taking Wrong Actions
AutoMod is deleting messages it shouldn't
AutoMod is deleting messages it shouldn't
1
Review your AutoMod filters in the dashboard
Open AutoMod in the dashboard and review each active filter. Look for overly broad banned word lists or regex patterns that could match legitimate messages.
2
Adjust filter thresholds
If you’re using spam detection, increase the message count or time window threshold to allow more messages before triggering. For caps, adjust the percentage threshold.
3
Check moderator exemption
Moderators (those with Administrator, Manage Messages, or Moderate Members permissions, or a configured mod role) are exempt from AutoMod by default. If a moderator’s messages are being filtered, verify their permissions.
4
Check the AutoMod log
The AutoMod log channel records every action with the matched filter and the original message. Use this to pinpoint exactly which filter is firing incorrectly.
Leveling XP Not Being Awarded
Members aren't gaining XP from messages
Members aren't gaining XP from messages
1
Confirm leveling is enabled
In the dashboard, go to Leveling and verify the module is toggled on. You can also check with
/level config.2
Understand the XP cooldown
Prowl applies a per-user cooldown between XP awards (default: 60 seconds) to prevent spam farming. A member sending many messages in quick succession will only earn XP for the first message in each cooldown window.
3
Check the XP rate
If the XP rate is set very low, members may not notice their XP gains. Use
/level config to check the current rate (default: 1.0).4
Check for bot messages
XP is only awarded for messages from real users. Messages sent by bots (including Prowl itself) never earn XP.
Getting More Help
If you’ve worked through the relevant steps above and your issue isn’t resolved, the Prowl community and support team are ready to help.Join the Discord
Get real-time help from the Prowl team and community in the support server.
Check System Status
See live uptime information and subscribe to incident alerts.