> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/troubleshooting.md).

# Troubleshooting

- [Bot didn't respond to a command](https://ticketking.xyz/docs/troubleshooting/bot-didnt-respond.md): When Ticket King doesn't reply to a command.
- [Members can't see a ticket channel](https://ticketking.xyz/docs/troubleshooting/members-cant-see-channel.md): A ticket opened but the member or staff can't see the channel.
- [Panel buttons do nothing or show "interaction failed"](https://ticketking.xyz/docs/troubleshooting/interaction-failed.md): Panel buttons do nothing, show 'This interaction failed', or do not open a ticket.
- [I can't access the dashboard](https://ticketking.xyz/docs/troubleshooting/cant-access-dashboard.md): Can't sign in, can't see a server, or the dashboard refuses an action.
- [A transcript is missing or empty](https://ticketking.xyz/docs/troubleshooting/transcript-missing.md): A close-log entry says a transcript is unavailable, or the link is broken.
- [My Bot Personalizer change isn't applied](https://ticketking.xyz/docs/troubleshooting/personalizer-not-applied.md): Bot Personalizer settings saved but the bot still looks default.
- [Auto-close fired when it shouldn't have](https://ticketking.xyz/docs/troubleshooting/auto-close-misfired.md): A ticket auto-closed when it shouldn't have, or didn't when it should.
- [A support role can't close a ticket](https://ticketking.xyz/docs/troubleshooting/support-role-cant-close.md): A staff member with the support role can't close a ticket.
- [A ticket name isn't allowed](https://ticketking.xyz/docs/troubleshooting/ticket-name-not-allowed.md): Discord rejected this ticket's name because it contains a word that isn't allowed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.