Discord Troubleshooting
Solutions to common Discord bot issues.
Bot Not Responding
Symptoms
- Bot doesn't respond to commands
- Commands show "Application did not respond"
- Bot appears offline
Solutions
-
Check bot status
- Is the bot online? (Green status indicator)
- Check Loyalteez Status Page
-
Run permission audit
/setup check -
Verify bot role hierarchy
- Bot role must be above managed roles
- Check Server Settings → Roles
-
Check channel permissions
- Bot needs Send Messages, Read Messages
- Check channel-specific overrides
-
Re-run setup if needed
/setup connect brand_id:YOUR_BRAND_ID security_key:YOUR_SECURITY_KEY
Rewards Not Processing
Symptoms
- Users run commands but don't receive LTZ
- Events fire but balance doesn't change
- "Reward failed" messages
Solutions
-
Check event is enabled
/config eventsLook for the event - is it enabled?
-
Check user status
/config user status:@userUser might be disabled
-
Check test mode
/config test-modeTest mode only rewards testers/admins
-
Check channel exclusions
/config channelsChannel might be excluded
-
Check cooldown
- User might need to wait
- Check event's cooldown setting
-
Check claim limits
- User might have hit max claims
- Check
max-claimssetting
-
Review audit log
/audit user:@user -
Verify brand has LTZ balance
- Check Partner Portal for brand balance
- Fund your brand wallet if empty
Role Effects Not Applying
Symptoms
- Role bonuses not added to rewards
- Multipliers not working
- Users with roles getting base rewards
Solutions
-
Verify Manage Roles permission
- Bot needs this permission
- Run
/setup check
-
Check role hierarchy
- Bot role must be ABOVE target roles
- Adjust in Server Settings → Roles
-
Refresh role sync
/config sync-roles -
Verify role configuration
/config role-bonus -
Check stacking mode
/config stacking
Stats Not Updating
Symptoms
/statsshows old data- Leaderboards not current
- Export shows missing data
Solutions
-
Allow time for aggregation
- Stats may take a few minutes to update
- KPI snapshots run at midnight UTC
-
Check test mode filtering
- Test mode activities don't count toward stats
/config test-mode -
Verify audit logging
/audit- If recent activity shows, logging is working
Third-Party Bots Not Detecting
Symptoms
- Mee6/Arcane level-ups not rewarding
- Integration shows enabled but not working
Solutions
-
Verify integration is enabled
/config third-party -
Check channel permissions
- Loyalteez must see third-party bot messages
- Check channel permissions
-
Verify correct bot
- Some bots have multiple versions
- Ensure you enabled the right one
-
Check event exists
/config events- Look for
mee6_level_upor similar
- Look for
Server Not Showing in Partner Portal
Symptoms
- Connected server not appearing in Partner Portal
- Can't configure from web interface
Solutions
-
Verify setup completed
/setup check -
Check Brand ID and Security Key were correct
- Brand ID: 42 characters, starts with
0x - Security Key: 64 character hex string
- Run
/setup connect brand_id:... security_key:...again if needed
- Brand ID: 42 characters, starts with
-
Check Supabase
- Look in
discord_server_configstable - Verify server_id and brand_id match
- Look in
-
Verify RLS policies
- Brand must have permission to read data
- Check Supabase RLS configuration
Drops Not Working
Symptoms
- Users can't claim drops
- Reaction drops not detecting reactions
- "Drop not found" errors
Solutions
-
Check drop hasn't expired
- Review lifespan setting
- Create new drop if expired
-
Check max claims
- Drop might have hit claim limit
-
Verify event is enabled
/config events -
Check correct emoji (for reaction drops)
- Must use exact emoji specified
-
Verify message exists (for reaction drops)
- Message might have been deleted
Setup Failed
Symptoms
/setup connecterrors- "Brand not found" messages
- Connection failures
Solutions
-
Verify Brand ID format
- Must be 42 characters
- Must start with
0x - Find in Partner Portal → Settings → Account
-
Check Partner Portal subscription
- Ensure you have an active subscription
-
Verify brand has LTZ balance
- Brand wallet needs funds for rewards
-
Check bot permissions
- Run
/setup checkfor permission audit
- Run
Diagnostic Commands
Use these to troubleshoot:
/test all # Full diagnostic suite
/test connectivity # Service connection test
/test permissions # Bot permission check
/test config # Configuration validation
/test reward event:EVENT # Dry-run reward test
/test report # Generate shareable report
Getting Help
-
Run diagnostics first
/test report -
Export relevant data
/audit export:true
/export type:config -
Contact support
- Partner Portal → Support
- Include diagnostic report and exports
- Discord Community