Web Dashboard & Bot Synchronization Delays

What Causes the Delay?

M4T3 uses a sophisticated caching system to ensure fast performance across thousands of servers. When you make changes in the web dashboard, these changes need to propagate through multiple cache layers before becoming active in the Discord bot.

Expected Delay Times

Configuration Changes

When you update settings in the web dashboard, expect:

• Up to 5 minutes for changes to reflect in the Discord bot
• This applies to all server configuration including:
  • Welcome messages
  • Auto-moderation settings
  • Anti-spam configuration
  • Social media integrations
  • Custom embed colors and settings

Scheduled Features

Certain scheduled features have additional considerations:

• Giveaways: Scheduling changes may take up to 5 minutes to be processed
• Leaderboards: Leaderboard updates follow the same 5-minute cache cycle
• Birthday notifications: Configuration changes follow standard cache timing

Cache System Details

M4T3 uses a 3-tier cache architecture:

1. Local Cache - In-memory storage for immediate access
2. Redis Cache - Distributed cache shared across bot shards
3. Database - Permanent storage with cache middleware

Changes from the web dashboard update the database first, then propagate through the cache layers during the next cache refresh cycle.

What This Means For You

Making Changes

• Make your configuration changes in the web dashboard
• Wait 5-10 minutes before testing in Discord
• If changes don't appear after 10 minutes, check your configuration again

Testing New Settings

• After saving changes in the dashboard, wait at least 5 minutes
• Test the functionality using Discord commands or triggers
• If still not working, verify the settings were saved correctly in the dashboard

Troubleshooting Steps

If Changes Don't Appear After 10 Minutes

1. Refresh the dashboard - Ensure your changes were actually saved
2. Check bot permissions - Verify M4T3 has the required permissions for the feature
3. Test in different channels - Some settings may be channel-specific
4. Check server roles - Ensure you have the required permissions to make changes

Emergency Changes

For urgent configuration needs:

• Use Discord slash commands when available (e.g., /admin settings)
• Discord commands bypass the cache delay for immediate effect
• Web dashboard changes will still take 5 minutes to synchronize

Features With Immediate Effect

Some Discord bot features work immediately:

• Manual commands (all /info, /community, /games commands)
• Economy transactions and balance updates
• Music playback controls
• AI command usage

These don't rely on cached configuration data and work in real-time.

Best Practices

• Plan configuration changes - Make multiple changes at once rather than individually
• Test during low activity - Wait periods are less noticeable during quiet server times
• Use Discord commands for urgent needs - When immediate changes are required
• Document your changes - Keep track of what was changed and when

Understanding this delay helps set proper expectations and prevents confusion when testing new configurations.