Troubleshooting - pup

Symptom	Check and next action
Server is missing	Confirm the signed-in account, bot installation and current server membership. Refresh the server picker.
Command does not appear	Check whether the interaction is enabled and Connection status reports successful registration. Context menus are optional.
Prefix command is ignored	Use the saved server prefix and exact command name. Check Message Content readiness and allowed interaction scope.
Gateway intents are degraded	Open Connection status to identify the missing required intent and affected enabled module, then update the Discord application and restart the bot.
Permission denied	Review Pup bindings, native actor permissions, bot permissions, role ordering and protected subjects.
Case exists but DM failed	Correct the member’s DM/block setting and retry the existing delivery from the dashboard.
Moderation log failed	Check that the configured channel still exists and the bot can view and write there. Use the existing recovery action.
Configuration is stale	Reload, inspect the latest settings, then reapply the intended change.
Roadmap says refresh delayed	The last valid public progress snapshot is being shown. This is not an application deployment failure.
Assistant is enabled but silent	In Community → Assistant, check Response channels. An empty list allows all eligible channels; a selected list also restricts dedicated chat channels. Check that Pup can view the channel and send messages, then mention Pup, reply to its message or use a dedicated chat channel.

Report the affected version, the visible stable diagnostic, the intended action and a minimal reproduction. Do not send tokens, private moderation content, member identifiers or unredacted provider payloads in public reports.