Bob the Bot Slash Command Outage
Resolved
Nov 20 at 07:00pm CST
Date: Nov 20, 2025 | ⏱ Duration: ~1 hour
🧭 Summary
For about an hour, Bob failed to respond to slash commands due to Discord rejecting global command updates.
The bot itself was healthy 🟢, but Discord’s API returned a persistent
50035 Invalid Form Body → BASE_TYPE_REQUIRED error during registration.
🧰 What We Tried
- 🔁 Re‑deployed containers and tokens (no change)
- 🧹 Cleared and re‑registered global commands
- 🧪 Verified code against the dev bot (worked fine there)
- 🏠 Registered commands per‑guild – confirmed success
🧩 Root Cause
A corrupted record in Discord’s global command database for Bob’s production application ID prevented any bulk overwrite from completing correctly.
This was a Discord‑side issue, not a code error. ⚠️
🛠️ Resolution
Catching and safely ignoring the benign API exception allowed Bob to continue starting up and attach all interaction handlers normally.
Once running, slash commands responded instantly again. ✨
Discord Support has been contacted to clear the bad record for a permanent fix. 📨
🕑 Timeline
- 5:23 PM CST – 🚨 First 502 monitor alert
- 5:30‑6:30 PM – 🔎 Multiple retries and redeploys; issue isolated to Discord API
- 6:50 PM CST – 🧩 Workaround deployed; bot fully operational
- 6:52 PM CST – ✅ Incident resolved
Bob is stable again across all 2,500 servers.
Root cause: Discord API corruption, successfully mitigated by code‑level handling while awaiting an official fix from Discord. Nonetheless, we apologize for the inconvenience.
Affected services