Troubleshooting
Diagnose sign-in, permission, setup, dashboard, evidence, and transcript problems with specific read-only checks.
- Audience
- moderator · senior reviewer · team lead · server admin · public appellant
- Availability
- free · premium preview · private beta access
- Maturity
- stable · alpha · partial
Last reviewed
On this page
Sign-in and server access
The server is missing or access stops after sign-in
What you see: Discord sign-in succeeds, but the intended server is absent, denied, or returns to selection.
What may be happening: The account may lack current server membership/authority, the server may not have runtime access, or the session may be stale.
What to do
- Confirm the same Discord account is in the intended server.
- Sign out and complete one fresh Discord sign-in.
- Ask a server administrator to verify the server's current ModFlow access.
- Escalate with the server name, safe route, time, and visible error—never credentials.
Permissions and visibility
A page, record, or action is denied
What you see: The dashboard opens, but a page, item, source, or control is hidden or denied.
What may be happening: Page permission, team role, record visibility, source-channel access, or action authority may be narrower than server access.
What to do
- Confirm the selected server and intended operator account.
- Identify whether the denial is page, record, source, or action access.
- Request only the missing team/Discord permission.
- Escalate to a server administrator without copying redacted material.
Setup and Discord prerequisites
A configured surface is missing or unhealthy
What you see: A Jail, Ban Review, role, channel, or log destination is absent, stale, or unusable.
What may be happening: A Discord object may have been deleted, renamed, moved above the bot, or lost required overwrites or permissions.
What to do
- Open System Health for the same server.
- Review the failing group and its repair guidance.
- Run only the supported setup repair for that surface.
- Escalate with the health group and repair result if verification still fails.
Commands and interactions
A command, menu, reaction, or button fails
What you see: The interaction is absent, disabled, denied, expired, or returns an uncertain result.
What may be happening: Registration, feature state, Discord permissions, team permissions, source visibility, or stale component state can block it.
What to do
- Use current Discord autocomplete or reopen the source Apps menu.
- Refresh the owning queue or record before retrying.
- Check for an existing action/execution result.
- Escalate with the command/menu name, server, record identifier, and visible response.
Dashboard state
Discord and dashboard disagree
What you see: A queue, panel, detail page, or summary shows different state from another surface.
What may be happening: One view may be stale, filtered, redacted, or showing a different lifecycle checkpoint.
What to do
- Confirm both surfaces refer to the same server and record identifier.
- Refresh the owning detail page and inspect its latest timeline event.
- Treat the stored record and execution result as authoritative.
- Escalate a reproducible mismatch with timestamps and safe screenshots.
Evidence and transcripts
Evidence or a transcript cannot be opened
What you see: A source message, attachment, recording, transcript, or playback artifact is missing, denied, partial, or still processing.
What may be happening: Consent/status, source-channel access, artifact visibility, processing failure, or local-file availability may limit it.
What to do
- Read the artifact's current status and access message.
- Verify consent and that the correct case/session is open.
- Record the artifact as unavailable or partial; do not substitute a private copy.
- Escalate through Contact with identifiers/status only, excluding sensitive content.
Safe escalation package
- Selected server and safe page/command name
- Record or job identifier when visible
- Current status and exact time
- Expected result and the last safe step completed
- A redacted screenshot only when it contains no private evidence or credentials
Moderation action failures
| Symptom | Check | Avoid |
|---|---|---|
| Member not found | Selected server, numeric ID, current membership. | Acting on a similarly named account. |
| Cannot moderate/manage | Bot role hierarchy, target owner/protected role, required Discord permission. | Granting Administrator blindly. |
| Invalid duration | Current field format, range, mutually exclusive add/total or subtract/total. | Guessing legacy syntax. |
| Action appears twice | History, Case, action execution, current Discord state, timestamps. | A third retry. |
| Primary succeeded, side effect failed | Voice state, log/DM, expiry job, purge, role cleanup. | Repeating the punishment to fix the side effect. |
| Undo chose unexpected action | Which still-effective action by the invoking moderator was newest. | Assuming /undo reverses warnings or any old action. |
| Mass action partial | Per-target result, invalid/truncated IDs, current ban/member state. | Repeating the entire batch. |
Cases, evidence, and review failures
| Symptom | Likely cause | Recover |
|---|---|---|
| Case not found | Wrong server, internal ID/Case number confusion, stale link, visibility. | Verify server and Case number/ID through Cases list. |
| Evidence hidden/redacted | Evidence visibility, source channel access, senior-only tier. | Use safe summary or hand off to authorized reviewer. |
| Source link dead | Message deleted, channel removed, permissions changed. | Record unavailability and request replacement provenance. |
| Case cannot decide/execute | Required permission, incomplete state/readiness, stale Case. | Refresh, review missing prerequisites, and use the owning control. |
| Appeal approved but action remains | Reversal not executed or failed. | Check original action state and approved appeal reversal result. |
| Ban Review approved but pending | Separate executor required or target/permission changed. | Do not duplicate request; use authorized execution/retry. |
| Wrong Case received evidence | Stale active Case selection or similar number. | Use authorized remove/move/correction and reattach once. |
Scheduled, automation, and voice evidence failures
| Symptom | Check | Response |
|---|---|---|
| Scheduled item still pending | Scheduled time/timezone, worker state surfaced to users, current queue state. | Do not create replacement until original non-execution is verified. |
| Cannot cancel | Whether item already left pending. | Refresh and follow the final/executing state; cancellation can race. |
| Automation rule silent | Enabled state, implemented trigger/condition, feature/permission. | Use manual review; do not broaden condition blindly. |
| Automation too noisy | Trigger window/condition and source fields. | Disable before tuning; recommendations never punish. |
| Soundcheck will not start | Feature access, staff permission, session conflict, voice/Stage context, consent setup. | Use status; do not bypass consent. |
| Recording/transcript missing | Final session, recording, transcription, publication, visibility, and storage statuses. | Record missing artifact; do not promise or reconstruct it. |
| Playback/download denied | Server, session source, viewer permission, artifact availability. | Handoff to authorized reviewer; copied links do not grant access. |
Settings, permissions, imports, and export failures
| Symptom | Check | Recover |
|---|---|---|
| Saved setting has no effect | Selected server, live object ID, bot/channel permission, fallback destination. | Restore prior value, test one event, recheck Health. |
| Team member still denied | Mapped role membership, team enabled/order, required dependency, action-specific permission. | Test exact allowed/denied operation after refresh. |
| Team member sees too much | Discord Administrator/protected role, broad team permission, channel overwrite. | Contain, restore least privilege, test with representative account. |
| Import source unhealthy | Channel/category ID, provider format, bot read history, last observed. | Repair source access before reconciliation. |
| Imported actor wrong/unknown | Provider versus actor, source message, confidence. | Keep unknown/low-confidence in review; do not invent attribution. |
| Export empty or too broad | Server, dataset, filters, user ID, date/time, permission. | Compare small dashboard query and regenerate narrowly. |
| Billing state unclear | Selected server, plan permission, hosted flow status, synchronization delay. | Do not repeat checkout; preserve visible status and use support. |
Recover newer workflow failures
A conversation, log, provider import, or MIRA action fails
What you see: The UI reports a delivery, channel, provider, permission, coverage, or Case-link error.
What may be happening: Discord destination access, DM privacy, expired provider authorization, feature gates, source visibility, worker readiness, or a release-dependent Case link may be unavailable.
What to do
- Confirm the selected server, feature status, plan, and operation-specific permission without retrying repeated writes.
- For Discord delivery, verify the exact channel or DM boundary and the bot's current view, send, and embed access.
- For Google or Microsoft imports, reconnect only through the authorized provider flow and reselect the intended file; never send tokens to support.
- For MIRA, check that the feature-status page still reports it as enabled for the server; coming-soon or gated deployments cannot run it.
- If a transcript or record points to the wrong Case, stop and report the identifiers to an administrator instead of copying the material elsewhere.