Troubleshooting

Common AttendiBot issues organized by symptom. For setup guidance, see Getting Started.

---

Sessions not being recorded

Signing not loaded

Symptom: Members join voice but no sessions appear in stats or leaderboards.

Cause: Signing keys are configured but not loaded in memory, so new sessions cannot be signed.

Fix:

1. Check Dashboard → Signing — status should show Signing active
2. Or Discord: /admin signing-status — should show signing active (survives redeploys)
3. If signing failed to load after a redeploy, contact support

Signing not configured

Symptom: /admin signing-status shows "not configured".

Fix: Generate keys first:

• Dashboard → Signing → Generate keys
• Or /admin generate-keys

Tracking mode is Off

Symptom: Bot is online but nothing tracks.

Fix: Set tracking mode to Allowlist, Denylist, or All:

• Dashboard → Settings → Tracking
• Or /admin tracking-mode mode:All

Channel not tracked (Allowlist mode)

Symptom: Some channels track, others don't.

Fix: Add channels to the allowlist:

• Dashboard → Settings → Tracking → Add channel
• Or /admin track-channel action:Add channel:#YourChannel

Session below minimum duration

Symptom: Brief joins don't create sessions.

Fix: Check Minimum session duration in fairness settings. Set to 0 to record all sessions.

Channel excluded (Denylist mode)

Symptom: Specific channels never track.

Fix: Remove the channel from the denylist or switch to Allowlist/All mode.

Members already in voice when tracking starts

Symptom: Tracking is enabled (or a channel is added to the allowlist) but members already sitting in that voice channel show no active session until they leave and rejoin.

Cause: Bootstrap sync ran before signing was active, or the Discord cache was not ready yet (most common right after a redeploy).

Fix:

1. Confirm signing is active: Dashboard → Signing, or /admin signing-status
2. Re-trigger sync: toggle tracking off/on, re-add the channel, or run /admin generate-keys / /admin rotate-keys if signing was the blocker
3. If the issue persists, have affected members switch voice channels briefly
4. After a redeploy, wait a few seconds — the bot retries bootstrap automatically on reconnect

---

Commands not appearing in Discord

Global registration delay

Symptom: Slash commands missing shortly after inviting the bot.

Cause: Discord can take up to an hour to propagate globally registered commands.

Fix: Wait and retry, or remove and re-invite the bot with both bot and applications.commands scopes.

Missing applications.commands scope

Symptom: Bot is in server but no slash commands at all.

Fix: Re-invite the bot with both bot and applications.commands scopes from attendibot.com.

---

Bot disconnects immediately

Symptom: Bot connects briefly then disconnects.

Fix: Re-invite the bot using the official Add to Discord button on attendibot.com.

---

Period reset skipped

Symptom: Period rollover did not run; signing may not be loaded.

Fix:

1. Check Dashboard → Signing or /admin signing-status
2. If signing is not active, contact support
3. The reset should complete within about a minute once signing is active

---

Dashboard issues

OAuth sign-in fails

Symptom: "Invalid redirect URI" or sign-in loop.

Fix:

1. Sign in with the Discord account that has Manage Server on your guild
2. Clear browser cookies for attendibot.com and try again
3. If the issue persists, contact support

Server not listed in guild picker

Symptom: Your server doesn't appear after sign-in.

Fix: You need Manage Server permission on that guild. Sign in with the account that has admin access.

---

Sessions stop after maintenance

Symptom: Sessions stop recording after a platform maintenance window.

Fix: Signing should recover automatically after redeploy. If /admin signing-status shows signing failed to load, contact support.

---

Log messages not posting

Symptom: Log destinations configured but no embeds in Discord channels.

Fix:

1. Verify the bot can Send Messages and Embed Links in the log channel
2. Check log type is enabled on the destination (/admin logs list)
3. For periodic logs (Leaderboard, AttendanceSummary), confirm interval is configured

---

Verification returns invalid

Symptom: Public verifier or /admin verify-session returns invalid.

Possible causes:

1. Session UUID is wrong or from a different server (use the session_id column from export CSV)
2. Signing keys were rotated or replaced without updating external verifiers
3. The stored signature needs to be refreshed for that record

Fix for repairable records: Dashboard → Signing → Repair session signatures. Run a dry run first, then apply. Discord: /admin repair-sessions

Archived period shows invalid signature

Symptom: Dashboard archived period page shows Signature invalid, or the public period verifier returns invalid.

Fix: Dashboard → Signing → Repair period snapshots. Run a dry run, then apply. Discord: /admin repair-periods

Note: Repair session signatures only fixes voice sessions, not archived period snapshots.

---

Getting help

• Review FAQ
• Visit attendibot.com/docs
• Contact support via the Discord link in the site footer (when configured)