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

# If a launch gets stuck

A paid launch is never lost. Here is what each outcome means and what to do about it.

## "Processing"

Your launch is on chain. The last details are being recorded and it completes on its own, even if you close the tab. Poll the status endpoint, or just reload your token page.

{% hint style="danger" %}
Do not pay again. A second payment creates a second token.
{% endhint %}

## "Resume launch"

If a launch fails partway, your browser keeps the payment signature and shows a **Resume launch** button. Resuming reuses the same payment: your mint address is deterministic, every address the launch created is already recorded, and any step whose accounts exist is skipped.

You are never asked to pay twice.

## "Nothing was charged"

If the response says `service_unavailable` with `charged: false`, the bundle did not land, nothing was charged, and no token exists. Get a fresh quote and submit again.

## Still stuck

If a launch stays unfinished after a resume, the payment signature is all that is needed to recover it. Keep it and get in touch on [X](https://x.com/launchonsf).

Two things are worth knowing while you wait. Your fees are not accruing anywhere you cannot reach, because until the pool exists there is nothing trading. And the payment can only ever produce one token, so there is no risk of a duplicate appearing later.


---

# 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://stonkfun.gitbook.io/stonkfun-docs/launching/recovery.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.