> 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-pro/core-features/error-handling.md).

# Error Handling

Show what failed and what the user can do next. Separate an unsent request, a pending transaction and a reverted receipt.

### Common cases

| Situation                                             | Next action                                                                      |
| ----------------------------------------------------- | -------------------------------------------------------------------------------- |
| Wrong network or deployment                           | Reconnect to the intended Pro network and configuration                          |
| Creation fee, economics or deployment version changed | Refresh the preview and rebuild within the user's accepted fee and launch limits |
| Insufficient balance or allowance                     | Check the asset and spender; confirm any approval before preparing again         |
| Deadline expired or output below the limit            | Refresh the quote and have the user review it; preserve agreed slippage limits   |
| Curve closed                                          | Read the lifecycle state and follow the pool-creation or recovery path           |
| Unknown Partner ID                                    | Correct the ID or explicitly choose no Partner                                   |
| Partner frozen or wrong claim account                 | Refresh the Partner's status and current Recipient                               |
| Recipient or metadata updates permanently disabled    | Explain that this permission cannot be restored                                  |
| Wallet account or network changed                     | Recreate the client and prepare for the selected account and network             |

Decode the contract error with the matching ABI and explain the action the user can take.

### Pending and failed transactions

`send` returns a transaction hash. Wait for a receipt with `status === "success"` before displaying completion. If waiting times out, resolve the existing hash or replacement before submitting again.

A revert rolls back that transaction's state changes, but the transaction can still consume network gas. A successful approval remains valid even if a later creation fails.

### Successful partial trades

A closing curve buy can succeed, spend less than requested and refund the rest. Read its actual fill; do not automatically trade the refund. A successful buy can also leave the launch waiting for sweep or pool creation. See [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation).

### Creation and protection errors

Use the [matching ABI](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/tax-and-pool-protection) to decode these errors.

| Error                          | Next action                                                                                                                                                                                                                                                          |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `PoolProtectionHashMismatch`   | Stop submission. Read and show the current protection policy, including its Resolver and rules data, and review the selected protection days; have the user confirm the change before rebuilding and previewing the final request. Do not silently refresh the hash. |
| `PoolTransferRestricted`       | Read the Token's current restriction and protection end state. Show which listed destination is blocked and when its restriction can end; pool-list membership alone does not mean a transfer is currently restricted.                                               |
| `ProtocolFeeRecipientConflict` | Stop creation and ask the deployment operator to correct the protocol fee recipient configuration.                                                                                                                                                                   |
| `InvalidProtectionDays`        | Use an integer from 0 to 365, in days.                                                                                                                                                                                                                               |
| `MinHoldingBelowFloor`         | Refresh the Holder minimum and review the new holding threshold.                                                                                                                                                                                                     |


---

# 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-pro/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.
