> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/3.-wallet-and-risk-control/transaction/transaction-resend.md).
# Transaction Resend
Solana transactions may fail due to network congestion or insufficient gas fees. Since the Solana blockchain does not provide a rollback mechanism for failed transactions, transactions must be manually resent. Please note that the funds and gas fees from the original transaction will remain frozen. To resend a transaction, **ensure your account has sufficient balance**. For assistance, please contact us at ****.
**Steps to Resend a Transaction:**
1. If a Solana transaction remains in a "pending confirmation" state for over 5 minutes, the system will display a "**Resend**" button.
2. Click the button to enter the resend interface, where transaction details, including the gas fee, will be displayed. Click "Confirm" to proceed.\ **Note: Funds from the original transaction are frozen, and insufficient account balance will prevent further action.**
3. Complete identity verification after clicking "Confirm."
4. Once the transaction is successfully resent, a notification will appear. After the transaction is completed, the funds from the previous transaction will be unfrozen, and the **gas fee will not be deducted**.
---
# 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://support.cregis.com/3.-wallet-and-risk-control/transaction/transaction-resend.md?ask=&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.
