Platform
Server Health Center
Find missing Discord resources, permission problems, incomplete setup, and delivery failures.
Getting started
Run a readiness scan
Review the weighted score, grade, severity counts, and category health across connectivity, permissions, configuration, runtime, account, and delivery.
Review the evidence
Open each warning or critical check, follow its direct remediation link, and add an acknowledgement or investigation note for staff.
Run safe diagnostics
Test one module or every module without changing member data; selecting a private channel sends only one labeled test embed.
Confirm the recovery
Scan again, compare score history for regressions, and download a server-scoped JSON report when support needs evidence.
Settings reference
Use this reference when you need to check what a setting does.
A 0–100 readiness score where critical connectivity and runtime checks contribute more than informational signals.
Excellent, Good, Needs attention, or Critical based on the weighted score.
Connectivity, permissions, configuration, runtime, account, and delivery readiness.
Private acknowledged, investigating, or resolved state plus a staff note; it does not hide the live result.
Immutable server-scoped score snapshots used to identify regressions.
Configuration validation for every module without Discord delivery or member-data changes.
Current checks plus the latest 30 scan summaries for the selected server.
Platform-administrator controls for public service incidents, maintenance, and component overrides.
How it works
Here’s what happens once you’ve finished setup.
- 1Dashboard
Runs live Discord and database-backed checks for the selected server.
- 2Scoring
Applies impact weights and records a scan snapshot.
- 3Administrator
Reviews evidence, records triage context, and follows the remediation link.
- 4Validation
Safe module diagnostics and a fresh scan confirm recovery.
Example
Reach Good or Excellent, clear all critical checks, run all module diagnostics, test member-facing delivery in a private channel, and export the report for the launch record.
Permissions
- View Channels
- Send Messages and Embed Links for channel delivery tests
Troubleshooting
Confirm the correct bot token, application, installation, and hosted process.
Restart the assigned worker and confirm its guild presence refreshes within five minutes.
Inspect scheduled, social, and webhook history from the prior 24 hours and correct permissions or credentials.
Select a replacement channel or role inside the affected module.
Review state is staff context only; fix the source condition and scan again.