> For the complete documentation index, see [llms.txt](https://guides.paynow.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.paynow.gg/integrations-and-commands/resending-commands.md).

# Resending Commands

When a command fails, you can re-run it for that one customer without refunding or re-granting the package. Resend after a server restart killed the original command, after a temporary issue stopped a customer receiving their purchase, or whenever the execution status shows **failed** or **pending**.

## How to resend

1. Go to **Content → Customers** and select the customer.
2. Open the **Inventory** tab.
3. Find the purchased package.
4. Click the **Info button ( ℹ️ )** next to it.
5. The **Command UI** opens, showing the **executed command**, the **game server** it ran on, and the **execution status**: Success, Failed or Pending.
6. Click **Resend Command**.
7. **Select the game server** to re-execute on.
8. Confirm.

You can only resend for packages that are still active. Expired packages no longer have access to their deliverables, and the option is unavailable.

{% hint style="warning" %}
**Read the Command UI before you resend.** It tells you whether the command actually ran, on which server, and whether it succeeded. Resending one that already succeeded gives the customer the item twice, and you don't get it back.
{% endhint %}

## If the command fails again

Check, in order:

1. The **game server is online** and properly connected. See [Game Servers](/integrations-and-commands/game-servers.md).
2. The **player exists**, and is **online** if the command requires it.
3. The **command syntax** is correct for the game.

If it keeps failing, check your server logs and contact [PayNow Support](https://discord.gg/paynow).

## You can't edit a command before resending

Resend re-runs the **exact command** that was originally executed. If you need a different one, either run the corrected command manually on your game server, or edit the package's commands and **re-grant the package** to the customer, which triggers the updated version.

Take the second route when the command was wrong for everyone rather than for this one customer. Fix the product first, or you'll be resending failures one at a time all week. For a group of affected customers, see [Bulk Assigning Products](/products/bulk-assigning-products.md).

## Preventing this

Test every product before selling it: buy it yourself and watch the command run. Use the customer placeholder rather than a hard-coded name. After any server incident, check the [order timeline](/orders-and-subscriptions/orders.md) to see what failed while you were down. Queued commands catch up when a server returns, so a brief outage usually resolves itself. Check before you resend.