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

# Troubleshooting

{% hint style="info" %}
This page lists the most common HyperStackz issues—wallet, deposits, orders, funding, and UI glitches—and how to fix them quickly.
{% endhint %}

***

### 1 • Wallet & Connection 🔐

#### “Connect Wallet” does nothing

1. Unlock MetaMask (or your browser wallet).
2. Switch to **Arbitrum One**.
3. Disable pop-up blockers and hard-refresh (`Ctrl + Shift + R`).
4. Still blank? Try a clean Chrome/Firefox profile.

#### Wrong-network banner

Add / switch to Arbitrum One:

* **RPC** `https://arb1.arbitrum.io/rpc`
* **Chain ID** `42161`

***

### 2 • Deposits & Balances 💰

| Symptom                              | Quick Fix                                             |
| ------------------------------------ | ----------------------------------------------------- |
| Deposit TX confirmed but balance = 0 | Wait ≈ 3 min (15 blocks) then refresh.                |
| TX stuck “pending” > 10 min          | Speed-up or cancel in wallet; resend with higher gas. |
| Sent wrong token / chain             | Open a Support ticket and provide the TX hash.        |

If a refresh briefly shows a zero balance, clear browser cache and reload.

***

### 3 • Orders & Strategy Execution 📤

#### Limit order hasn’t filled

* The market price may simply not have reached that level yet—check the order book for your limit.

#### Take-profit (TP) didn’t trigger

* TP fires only when **Price ≥ AEP × (1 + TP %)** 

***

### 5 • Dashboard & UI Glitches 🖥️

| Problem                      | Quick Fix                                          |
| ---------------------------- | -------------------------------------------------- |
| Charts won’t load            | Disable ad-block / privacy extensions and refresh. |
| Points not updating          | Leaderboard syncs every 10 s—give it a moment.     |
| “Something went wrong” toast | Copy the error ID and send it to Support.          |

***

### 6 • When to Contact Support 🆘

Email **<support@hyperstackz.com>** or open a Discord ticket if:

* A transaction is stuck > 30 min with no order created.
* Vault equity diverges > 0.5 % from Hyperscan.
* Funds were sent to the wrong chain or token.
* A UI bug prevents pausing or stopping a strategy.

Include:

1. Vault wallet address
2. TX hash (if deposit / withdraw)
3. Approx. UTC time of the issue
4. Screenshot or recording
5. Browser & wallet versions

***

{% hint style="warning" %}
Most issues resolve with a network switch, cache clear, or waiting for chain finality.\
**Do not** spam extra transactions—open a ticket and share your TX hash if unsure.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://hyperstackz.gitbook.io/hyperstackz-docs/support-and-safety/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.