> 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/panels/resend-a-panel.md).

# Resend a panel

If the panel message gets deleted or you want a fresh copy.

When the panel message in Discord disappears (mod deleted it, channel was cleared, etc.), members can no longer interact with it. The fix is to resend.

## The resend action

From the **Panels** page:

1. Find the panel you want to resend.
2. On the panel card, click **Resend**.
3. Confirm.

The bot posts a fresh copy of the panel in its configured channel. Everything else stays as it was.

<figure><img src="https://1268186137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrnuG1qjzbOoh0efVpoK8%2Fuploads%2Fgit-blob-a52426750d611064047e7d155926f322f69e96eb%2Fresend-panel-process.gif?alt=media" alt="Resending a panel from the Panels page"><figcaption></figcaption></figure>

## When to use it

* The panel message is missing or visibly broken in Discord.
* You want to bump the panel to the bottom of the channel (new messages have pushed it up).
* You made significant edits and want a fresh post so members notice.

## What's preserved

Everything except the previous panel message:

* Options.
* Per-option settings.
* Open tickets.
* Audit history.
* Templates.

## Resend vs Move

* **Resend.** Same channel, new message.
* **Move.** Different channel. See [Move a panel](https://ticketking.xyz/docs/panels/move-a-panel.md).

## Common issues

{% hint style="warning" %}
**The resend posted but the old message is still there.** Ticket King could not find the previous message because it was deleted by hand or the channel was cleared. Delete the leftover yourself if needed.
{% endhint %}

{% hint style="danger" %}
**Permission error on resend.** If you see "I don't have permission to send messages in that channel," the bot cannot post in the panel's channel. Make sure the bot has **View Channel**, **Send Messages**, and **Embed Links** there, then try again.
{% endhint %}

## Related

{% content-ref url="/pages/q4FbZhLgL3ynrDoRrdTQ" %}
[Move a panel to another channel](https://ticketking.xyz/docs/panels/move-a-panel.md)
{% endcontent-ref %}


---

# 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/panels/resend-a-panel.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.
