Social Media Integration Not Working

Common Social Media Issues

M4T3 supports notifications from multiple platforms: Twitch, YouTube, Instagram, Twitter, Reddit, and RSS feeds. When these integrations stop working, it's usually due to configuration issues, API limitations, or service-specific problems.

Recent Updates: M4T3 has implemented 2025 best practices including circuit breakers, rate limiting with exponential backoff, and improved reliability across all social platforms.

Supported Platforms

Streaming Platforms

• Twitch - Live stream notifications when streamers go live (800/min rate limit)
• YouTube - New video upload notifications from channels (50/hour rate limit)

Social Networks

• Instagram - New post notifications from accounts (30/min rate limit with validation)
• Twitter - New tweet notifications from accounts (15/15min rate limit)
• Reddit - New posts from subreddits (60/min rate limit)

Custom Content

• RSS Feeds - Custom RSS/Atom feed notifications (120/min rate limit)

Setting Up Social Media Integration

Method 1: Using the Web Dashboard

1. Go to your M4T3 Dashboard (https://m4t3.com/dashboard)
2. Select your server
3. Navigate to Guild Settings > Social Media
4. Choose the platform you want to configure
5. Enter the required information:
   • Twitch: Username or channel name (use login name, not display name)
   • YouTube: Channel ID (UC...), username, or handle (@username)
   • Instagram: Username (public accounts only, validated for accuracy)
   • Twitter: Username (without @)
   • Reddit: Subreddit name (without r/)
   • RSS: Feed URL (must be valid XML)
6. Select the Discord channel for notifications
7. Customize the notification message (optional)
8. Click "Save Configuration"
9. Test the integration

Method 2: Using Bot Commands

1. Use /setup social setup command in Discord
2. Select the platform you want to configure
3. Follow the interactive prompts to:
   • Enter username/channel information
   • Choose notification channel
   • Set custom message (optional)
4. Save the configuration
5. Test the integration

Common Problems and Solutions

No Notifications Appearing

Check Configuration

1. Verify usernames/IDs: Ensure exact spelling and correct format
2. Test channel permissions: Bot needs send message permissions
3. Check notification channel: Verify the channel still exists
4. Check dashboard settings: Confirm integration is enabled
5. Wait for sync: Changes can take up to 5 minutes to propagate

Platform-Specific Issues

Twitch Issues (Recently Fixed):

• Username vs Display Name: CRITICAL - Use the actual Twitch login username (user_login), not display name (user_name). This was a major bug recently fixed.
• Case sensitivity: Use lowercase usernames for best results
• Stream delays: Notifications appear 1-2 minutes after going live
• API rate limits: 800 requests per minute with circuit breaker protection
• Duplicate notifications: Fixed - now only shard 0 processes notifications

YouTube Issues (Recently Fixed):

• Channel ID format: Modern channels use Channel IDs starting with "UC"
• Handle resolution: @username handles now properly resolved via search API
• Legacy usernames: Old YouTube usernames rarely work, use Channel ID instead
• Upload delays: YouTube API has 5-15 minute delays for new videos
• Private/unlisted videos: Only public videos trigger notifications
• Channel detection: Now properly detects channel identifier type (UC vs @ vs legacy)

Instagram Issues (Recently Fixed):

• Username validation: NEW - M4T3 now validates that returned posts match configured username
• Account privacy: Only public accounts can be monitored
• False notifications: Fixed issue where wrong user posts were being sent (e.g., "Innocenceonherface" instead of "foxiekt")
• RSS feed validation: Now validates RSS items match configured username before processing
• Content restrictions: Some post types may not trigger notifications
• Rate limiting: 30 requests per minute with exponential backoff

Twitter Issues:

• Account suspension: Suspended accounts won't trigger notifications
• Protected tweets: Private accounts cannot be monitored
• API changes: Uses RSS feeds for reliability
• Rate limits: 15 requests per 15 minutes with circuit breaker

Reddit Issues:

• Subreddit name: Use exact subreddit name without r/ prefix
• Private subreddits: Only public subreddits can be monitored
• Banned subreddits: Cannot monitor banned or quarantined subreddits
• Content filters: NSFW content may be filtered
• Rate limits: 60 requests per minute

RSS Issues:

• Feed URL validity: Must be accessible and return valid XML
• Feed format: Must be valid RSS 2.0 or Atom format
• SSL certificates: HTTPS feeds with invalid certificates may fail
• Feed updates: Some feeds update infrequently
• Rate limits: 120 requests per minute

Duplicate Notifications (Fixed)

Recent Fix: M4T3 now runs social integration only on shard 0, eliminating duplicate notifications that occurred when multiple shards processed the same content.

1. Check multiple configurations: Ensure the same account isn't configured multiple times
2. Verify notification channels: Make sure different configurations use different channels
3. Review webhook settings: Multiple webhooks can cause duplicates
4. Shard processing: Now handled automatically (shard 0 only)

Delayed Notifications

1. Expected delays: Most platforms have 2-15 minute delays
2. API rate limits: Circuit breakers prevent cascade failures
3. Cache refresh: M4T3 checks for updates every 5-15 minutes
4. Platform status: Check if the social platform is experiencing issues
5. Circuit breaker: May temporarily pause checks if too many failures occur

Advanced Troubleshooting

New Reliability Features

• Circuit Breakers: Prevent cascade failures with CLOSED/OPEN/HALF_OPEN states
• Rate Limiting: Exponential backoff prevents API exhaustion
• Unified Metrics: Comprehensive monitoring via /admin dashboard command
• Deduplication: Cycle-based caching prevents duplicate API calls

Testing Individual Platforms

1. Use test commands: /setup social list to verify specific integrations
2. Check API responses: Look for error messages in bot logs
3. Verify API keys: M4T3 manages API access automatically
4. Monitor rate limits: Circuit breakers handle rate limit management
5. Check metrics: Use dashboard to view success/failure rates

Configuration Validation

1. Double-check usernames: Copy-paste to avoid typos
2. Verify platform URLs: Ensure the account/channel exists and is public
3. Test notification channel: Send a test message to verify permissions
4. Review bot roles: Ensure M4T3 has necessary Discord permissions
5. Wait for propagation: Allow 5 minutes for changes to sync

When to Contact Support

• Notifications stopped working for all platforms after recent updates
• Circuit breaker remains OPEN for extended periods
• Error messages persist after configuration fixes
• Platform-specific issues affecting multiple servers
• Suspected API or service outages

Best Practices

Configuration Management

• Use exact usernames: Especially important for Instagram and Twitch
• Regular testing: Periodically verify integrations work
• Monitor changes: Watch for platform username/URL changes
• Backup settings: Document your configurations
• Check validation: Ensure usernames are properly validated

Notification Optimization

• Dedicated channels: Use separate channels for different platforms
• Custom messages: Personalize notifications for your community
• Role mentions: Use role pings for important notifications
• Embed customization: Configure embed colors and formatting
• Rate limit awareness: Don't exceed platform limits

Performance Considerations

• Limit integrations: Circuit breakers manage load automatically
• Stagger configurations: Built-in rate limiting handles timing
• Monitor metrics: Check M4T3 dashboard for detailed statistics
• Regular maintenance: Review and clean up unused integrations
• Reliability monitoring: Watch circuit breaker status in dashboard