BabelBotBabelBot Docs

Discord translator bot troubleshooting

Fix cases where a Discord translator bot is not working with step-by-step checks for settings, bridges, and quotas.

Discord translator bot quick configuration check

Run these in Discord first:

/server view
/language list
/channel view channel:#general
/reply-preference view
/quota

If everything looks correct but issues persist, work through the sections below.

Issue catalog

Reducing noisy output

Too many target languages or channels can flood the channel. Fix it in two steps:

1. Switch to thread mode

/reply-preference thread

Or set this in the dashboard under Reply preference.

2. Tighten scope

  • Remove low-priority target languages
  • Disable channels where translation adds little value (admin, logs, bots)
  • Keep bridges only where you actually need cross-language exchange

Bridge debugging

Check in order:

  1. /bridge list shows the bridge
  2. Source and target channels and languages are correct
  3. BabelBot has view and send permissions in both channels

Quota reached

When you hit the monthly limit, translations stop until you add capacity or the next billing period starts.

  • /quota shows usage and remaining capacity
  • /upgrade opens dashboard billing for the current server
  • Dashboard Billing & upgrades lets you buy top-up packs, upgrade, and manage the subscription

Quota backend outage runbook

Use this runbook when quota storage is unavailable and quota checks cannot be read or written reliably.

Identify the outage

Confirm the issue before making changes:

  1. Run /quota and check for temporary data unavailability responses
  2. Watch for in-channel warning messages about quota verification or usage recording
  3. Confirm behavior by sending one test message in a translation-enabled channel

Expected behavior by plan type

During a quota backend outage, BabelBot behaves differently by tier:

  • Metered tiers (FREE and STARTER): Translation pauses while quota cannot be verified
  • Unlimited tiers (ADVANCED and LIFETIME): Translation continues, but usage recording can lag

Operator actions

Keep the impact controlled while quota storage recovers:

  1. Post a short server update so moderators know this is a temporary quota service incident
  2. Avoid repeated retry tests that can create channel noise
  3. Re-check /quota every few minutes until it returns normal usage data
  4. Send one final test message after recovery to verify normal translation flow

Escalate if recovery is delayed

If quota behavior is still degraded after repeated checks, contact support with your server ID, approximate start time of the outage, and a screenshot of the latest /quota response.

Image translation (paid feature)

Image text translation is a paid capability. On the free tier, text translation works normally; only image translation is unavailable.

Contact support

Contact support when:

  • Your settings match the docs but behavior does not
  • Issues are inconsistent across channels
  • Dashboard actions fail repeatedly

Support: discord.gg/gjKmEnvkxx

On this page