Troubleshoot the Discord Bot

Overview

Blocked popup, install URL, no/failing channels, missing add-on data, save error, test message, and reconnect/remove. Discord Bot add-on, Owner. Use this guide to isolate the cause safely before repeating the action. Add-ons unlock organization features, while subscription and billing surfaces control plan availability and checkout state.

Identify the symptom

Blocked popup, install URL, no/failing channels, missing add-on data, save error, test message, and reconnect/remove. Discord Bot add-on, Owner. Note the exact point where the actual behavior differs from what you expected.

Do not repeatedly submit, delete, publish, reconnect, or purchase while the result is uncertain. First verify whether the previous action completed in another tab, activity list, Audit Log, or external platform.

Checks to make in order

Start in Add-On Management or Subscription & Billing. Keep the affected item open where possible so you can compare the state after each check.

1. 1
   Check 1: Blocked popup

   Review blocked popup and choose the value that matches your intended result.

2. 2
   Check 2: Install URL

   Review install URL and choose the value that matches your intended result.

3. 3
   Check 3: No/failing channels

   Review no/failing channels and choose the value that matches your intended result.

4. 4
   Check 4: Missing add-on data

   Review missing add-on data and choose the value that matches your intended result.

5. 5
   Check 5: Save error

   Save error.

6. 6
   Check 6: Test message

   Review test message and choose the value that matches your intended result.

7. 7
   Check 7: Reconnect/remove

   Review reconnect/remove and choose the value that matches your intended result.

Safe recovery

After correcting the cause, refresh the page and repeat the smallest safe action that can prove the workflow works. The issue is resolved when the organization shows the intended add-on, plan, allowance, or purchase state.

If a retry could publish, delete, charge, revoke access, retire a public address, or send a message twice, contact an owner or support instead of guessing.

• Confirm owner access and whether the feature or billing flow is currently released.
• Refresh after a plan or add-on change so organization allowances can be recalculated.
• For payment issues, record the checkout result and contact support without sharing card or account secrets.

If you still need help

Send support the organization name, route, affected item ID, timestamp and timezone, exact message, screenshot, and reproducible steps. Include the relevant System Status or Audit Log entry when available.

Never send passwords, verification codes, cookies, access tokens, API keys, payment details, or other secrets.

Availability and access

Related guides