Discord translator bot troubleshooting

This page is problem → checks → fix. For why skips happen by design, read How BabelBot Works.

Quick configuration check

Before deep debugging, confirm in the dashboard:

Quick configuration checks before troubleshooting translations

Check	Where
Translation enabled	Overview
At least one target language	Settings → Target languages
Test channel not excluded	Settings → Channel rules (verify with a test message)
AI quota remaining	Billing & upgrades
Reply mode matches expectation	Settings → Reply preference

Run /help in Discord for admin command reminders.

Issue catalog

Reduce noisy output

Problem: Too many replies or threads.

1. Settings → Reply preference → Reply in threads
2. Remove low-priority target languages
3. Tighten channel rules so fewer channels auto-translate
4. Remove unused bridges

Bridge debugging order

1. Bridge visible in dashboard
2. Languages match how your community uses each channel
3. Permissions in every linked channel
4. Test text (not link-only) in each direction
5. Check Overview activity chart for bridge-sourced usage

Quota reached

When AI quota for the period is exhausted:

• Dashboard → Billing & upgrades shows usage
• /upgrade links to billing
• Plain text may still translate on in-house fallback (eligible tiers)
• Image and flag/context-menu flows still need AI

Mitigation: fewer languages, fewer active channels, disable flag reactions, upgrade plan.

Quota backend outage

Use when usage will not load or in-channel warnings mention quota verification.

Identify

1. Billing & upgrades — usage fails to load or looks stale
2. Send one test message in an enabled channel
3. Note whether translations pause entirely or only usage is wrong

Expected behavior

Expected translation behavior during a quota backend outage by tier

Tier type	Translation during outage
Metered (Free, Pro, Ultra)	May pause while quota cannot be verified
Unlimited (Legacy Ultra, Lifetime)	May continue; usage recording can lag

Operator actions

1. Tell moderators it is a temporary quota service issue
2. Avoid spamming retry tests in public channels
3. Re-check billing every few minutes
4. After recovery, one test message to confirm normal flow

Escalate

Contact support with server ID, outage start time, and a billing page screenshot if degraded more than a short period.

Contact support

Reach out when:

• Settings match these docs but behavior does not
• Issues are inconsistent across channels with the same rules
• Dashboard or checkout fails repeatedly

Include: server ID, channel ID (if relevant), message ID (if relevant), time range, and billing screenshot if quota-related.

Support: discord.gg/gjKmEnvkxx