# Transaction Status

The outcomes of copy trading transactions are categorized into three main states: Successful, Failed, and Timed Out.

**Successful**

A "Successful" status indicates that the user's transaction has been successfully sent and packaged onto the blockchain by the node.

**Failed**

A "Failed" status indicates that the user's transaction has either failed to be sent or encountered issues during the node packaging process.

Failure reasons are categorized as follows:

The reasons for failure are defined as follows:

1. **Task Parameter Constraints**:
   1. **GasPrice Exceeded Limit**: Example: Current GasPrice (60.00 GWEI) > Maximum GasPrice Limit (50.00 GWEI)
   2. **GasLimit Exceeded Limit**: Example: Current GasLimit (3,000,000) > Maximum GasLimit Limit (1,000,000)
2. **Proxy Wallet Balance Issues**:
   1. **Insufficient Eth/BSC Balance**: Example: Required Eth balance for task execution (0.0125 ETH) > Current available Eth balance (0.005 ETH)
   2. **Insufficient Token Balance**: Example: Required ABC balance for task execution (100 ABC) > Current available ABC balance (0 ABC)
3. **Blockchain Node Restrictions**:
   1. **Simulation Failure by Packaging Node**: The packaging node's simulated execution failed, possibly due to insufficient slippage, paused transactions, blacklists/whitelists, or anti-front-running mechanisms.
   2. **Hash Data Transmission Failure**: Hash data transmission failed due to node congestion.
   3. **Transaction Failure**: Unusual transaction errors and on-chain failures. For details, please refer to the blockchain explorer.
4. **User Protection Measures**:
   1. **Transaction Blocked**: If the user's profit from selling does not cover the gas fees, 1STEP will block the transaction to prevent further loss.

**Timed Out**A "Timed Out" status indicates that a user's transaction has not been confirmed on-chain within 10 blocks. 1step will then consider the transaction as timed out.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://1stepapp.gitbook.io/1step-docs-en/review-results/transaction-status.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.