# Panel buttons do nothing or show "interaction failed"

When a member clicks a panel button, the bot almost always responds. It either opens a ticket, shows a form, or replies with a short message that explains why it could not. Two different things can go wrong, and they have different causes. Work out which one you are seeing first.

## The button shows "This interaction failed" or nothing happens at all

This means the bot never answered the click. Discord needs the bot to answer within a few seconds. If it does not, Discord shows the generic "This interaction failed" message, or the click simply appears to do nothing.

### The bot is offline

Find Ticket King in your member list. If it shows as offline (grey), its connection to Discord is down. It reconnects on its own once the problem clears. You can check the [status page](/docs/get-help-and-community/status-page.md) while you wait.

### The bot is no longer in your server

The bot cannot answer a click if it is not in the server anymore. Another bot, such as an anti-raid bot, may have removed it, or it may have been removed by mistake. Re-invite Ticket King with the [invite link](https://ticketking.xyz/invite?via=docs).

### The bot cannot see the channel the panel is in

If the Ticket King role loses View Channel in the channel that holds the panel, the bot can no longer act on clicks there. Give the Ticket King role View Channel in that channel.

### The panel is a very old format

After a panel-format change, a very old panel message in Discord can stop responding. Resend the panel to replace it with a current one.

→ [Resend a panel](/docs/panels/resend-a-panel.md)

### Discord or the bot was briefly slow

During a busy period a reply can arrive a moment too late. This is rare. Try again.

## The bot replied, but no ticket opened

Here the bot did answer. Read its message, because it tells you what is wrong. The common reasons:

* **You are blocked.** One of your roles is on the **Blocked Roles** list. Check it in **Settings**, then **Blocked Roles**.
* **You already have a ticket open.** If **Max Active Tickets Per User** is 1 (the default), clicking again points you to your existing ticket instead of opening a new one.
* **The server is at its ticket limit.** If the server has hit **Max Active Tickets** (default 500), the bot asks you to try again later.
* **The category is full.** Discord caps a category at 50 channels. The bot tries your other configured categories in order. If all are full, it replies that the server has too many channels to create a ticket.
* **Required Roles does not include you.** <i class="fa-crown">:crown:</i> If the option has **Required Roles** set and you have none of them, the option will not open. Required Roles is a Premium feature, so it only takes effect on a premium server.
* **The bot is missing a permission.** The reply names the missing permission. Grant it to the Ticket King role.
* **The bot's role sits too low.** To open a ticket the bot creates a channel and gives the support role access to it. The Ticket King role must sit above any support role it grants. Move it up in **Server Settings**, then **Roles**.

→ [Limits on open tickets](/docs/tickets/limits-on-open-tickets.md)

## How to investigate

* **Check the Opened Tickets log channel.** If tickets are being created, the open log shows them.
* **Check the Audit Log.** A panel or ticket entry tells you the click was processed.
* **Test as a staff member.** Staff with Manage Channels or Manage Server are not held back by some limits and role gates. If it works for them but not for a member, the cause is a role or limit on the member.
* **Test with a basic role.** Try with an account that has only its baseline roles to rule out role-related causes.

## Related

{% content-ref url="/pages/jqRuZ7otlMbsCHzNqzss" %}
[Bot didn't respond to a command](/docs/troubleshooting/bot-didnt-respond.md)
{% endcontent-ref %}

{% content-ref url="/pages/ynFOutOBHv7WcfyqMTbW" %}
[Limits on open tickets](/docs/tickets/limits-on-open-tickets.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/troubleshooting/interaction-failed.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.