> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/error-handling.md).

# Error Handling

Identify transaction failures and choose the correct recovery action.

Handle typed SDK errors before retrying. Continue only when the receipt status is "confirmed". After an RPC timeout, check the transaction hash before resubmitting. If the user rejects signing, wait for a new request. Refresh the affected state, quote or allowance before retrying.

Handle each error according to its cause:

<table><thead><tr><th width="321">Error</th><th width="96">Meaning</th><th width="303">What to do</th></tr></thead><tbody><tr><td><code>LaunchpadTradingClosedError</code></td><td>Curve reached the boundary</td><td>Refresh Graduation status. Route to V4 only after poolCreated; otherwise show trading as unavailable.</td></tr><tr><td><code>LaunchpadTradeFeeConsumesInputError</code></td><td>Fees consume the gross amount</td><td>Refresh the fee quote. If snipe tax is active, wait for it to decay; do not increase input as a workaround.</td></tr><tr><td><code>LaunchpadInsufficientQuoteReserveError</code></td><td>Sell exceeds real reserve</td><td>Reduce size</td></tr><tr><td><code>LaunchpadSlippageError</code> / <code>LaunchpadDeadlineExpiredError</code></td><td>Stale quote</td><td>Get a fresh quote and deadline, then rebuild with user-confirmed slippage. Never raise tolerance automatically.</td></tr><tr><td><code>LaunchpadCreatorDeniedError</code></td><td>Per-account ban</td><td>Not retryable by that account</td></tr><tr><td><code>LaunchpadLaunchNotPermittedError</code></td><td>Global gate closed</td><td>Retryable if whitelisted or reopened</td></tr><tr><td><code>LaunchpadEconomicsHashMismatchError</code></td><td>Launch terms changed</td><td>Refresh the parameters, ask the user to confirm the updated terms, then rebuild the hash.</td></tr><tr><td><code>LaunchpadApprovalRequiredError</code></td><td>Missing allowance</td><td>Approve the <code>spender</code> it names — forwarder for <code>launchAndBuy</code>, factory for <code>createToken</code>, curve for trades</td></tr><tr><td><code>LaunchpadPhaseUnavailableError</code> from <code>prepareGraduate</code></td><td>Usually already graduated by someone else's trade</td><td>Re-read the status; <code>launchpadGraduateIsIdempotentSuccess</code> means done, not failed</td></tr></tbody></table>

### Wallet and Holder recovery

| Situation                                               | Action                                                                                                                  |
| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Wallet rejected, missing account or wrong chain         | Let the user reconnect/switch and prepare again; do not automatically resend                                            |
| Deployment verification failed                          | Stop writes and reconcile the complete configuration/ABI version                                                        |
| Approval succeeded but the buy fails for allowance      | Check the actual `quoteInRaw`, asset, spender, account and chain; refund previews do not reduce the upfront pull        |
| Holder integration absent / quote asset disallowed      | Disable that feature for this deployment/asset; do not substitute Testnet addresses                                     |
| Unknown/unregistered distributor                        | Resolve the token's registered binding; do not infer one from an arbitrary fee recipient                                |
| Proof mismatch                                          | Validate recipient, both asset amounts and proof against the on-chain epoch root; refetch for the correct project/chain |
| Already claimed, excluded, expired or rolled-over epoch | Refresh authoritative chain state and remove the unavailable action                                                     |
| Batch claim reverted                                    | Identify stale/invalid allocations and rebuild the batch; it is all-or-nothing                                          |
| Harvest returns zero                                    | Display no collectible revenue; harvest does not publish an epoch or pay holders                                        |

For a transaction timeout, check the known hash before retrying. After an uncertain creation, also reconcile the consumed salt and creation events. Use [Holder claim checks](https://docs.peach.ag/documentation/arc/launchpad/core-features/fees-and-claims) for complete recovery sequences.


---

# 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://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/error-handling.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.
