> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pup.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Recover from common access, registration and delivery failures.

| 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 Health 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.     |
| 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.                 |

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.