> For the complete documentation index, see [llms.txt](https://docs.renzofinance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.renzofinance.com/help/troubleshooting.md). # Troubleshooting Common issues and how to fix them #### Deploying a position **Deployment failed** This usually means there isn't enough idle USDC in your HyperCore balance. Opening a position needs USDC available that isn't already in use elsewhere in your account. To fix it: * Check your available USDC balance on HyperCore * Add more USDC, or lower the amount you're deploying * Try again **Balance shows zero** The app reads your USDC balance on HyperCore. If it shows 0, your funds are probably still on another chain or wallet. To fix it: * Check that your USDC is on HyperCore, not just in your wallet on another chain * If it isn't, use the **Bridge** button in the app to move funds in * If you just bridged, wait a few minutes and refresh. Bridges can take time to settle **Can't select a risk preset** Each preset has its own minimum deposit, shown in the app. If your amount is below the minimum for a preset, you can't select it. Increase your deposit or choose a different preset. #### Trades and fills **Transaction failed or order only partly filled** To protect you from bad prices, Renzo limits slippage on the perpetual side to 0.5%. Before each order, it checks the order book depth and available liquidity, and only fills what it can within that limit. When the market is thin or moving fast, an order may fill partly or not at all rather than execute at a worse price. This is more likely on smaller markets, where the order books are thinner. To fix it: * Wait a few minutes and try again, as liquidity often recovers quickly * Try a smaller amount * If a partial fill left your hedge uneven, the hedge guard will catch it. On Auto it rebalances for you; on Manual you'll be notified to act #### Position management **My guards aren't acting** Check two things: * **Your trading key.** Guards only work while your trading key is active. If it has expired or been revoked, your position stays open but unmanaged. Renew it from **Settings** on the portfolio page. See Trading Key * **Your automation settings.** A guard set to Manual won't act on its own; it notifies you instead. Switch it to Auto from the settings icon on the portfolio page. See Automations **My position was exited** The yield guard exits to USDC when funding has been net negative over its window (two days by default). This is expected behavior when funding turns against the position. You can open a new position once funding recovers. See Automations **My APR dropped** Your yield comes from funding, which changes hourly with market demand. A lower APR usually means funding has dropped, not that something is wrong. Check the live and 30-day average APR in the app. #### Withdrawals **My withdrawal is waiting on me** Withdrawals always need your signature. Your trading key can't move funds out of your account. Check your wallet for a pending signature request. #### App issues **Page not loading or not updating** * Refresh the page * Clear your browser cache, or try a private window * Disconnect and reconnect your wallet * Try a different browser, or turn off browser extensions that may block scripts * Check your internet connection **Wallet won't connect** * Make sure your wallet extension is unlocked * Refresh the page and try connecting again * Check that your wallet is on the right network * Try a different browser --- # 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.renzofinance.com/help/troubleshooting.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.