Diagnose connection, data, Discord, permission, and integration problems.
Start with the narrowest failing surface. Confirm its connection, permissions, and latest successful event before changing several settings at once.
Diagnose the failing surface
Confirm murphy_platform is running, verify that its token matches Settings > Server Connection, check outbound HTTPS access, the heartbeat interval, server clock, Platform Logs, and host logs around the last heartbeat.
Confirm a player joined after the resource started. Then verify the identity provider, relevant sync interval, installed compatible plugin, and staff permission. If only one module is missing, troubleshoot that resource instead of reinstalling Platform.
Confirm the bot is still in the correct guild, can view and send in the configured channel, and can manage the destination role. Refresh channel and role mappings after changing the Discord structure.
Check that the server plan includes the feature, the staff membership belongs to the current workspace, and the assigned role grants the required area and level.
For Tebex, inspect the original transaction and delivery. For API calls, check key status, scope, server, and rate limits. For webhooks, validate the receiver URL, signature, response code, and delivery log.
Report a reproducible problem
Record the server workspace, affected player or record when appropriate, page, approximate time, action taken, expected result, actual result, and relevant non-secret log entries. Never include resource tokens, API keys, webhook secrets, authentication tokens, private ticket content, or sensitive player information in a public report.