# Troubleshooting Guide {% embed url="" %} ## Network Connectivity Issues ### High Latency and Slow Trading Experience **Problem:** Trades execute slowly, interface feels laggy, or transactions take longer than expected to process. **Cause:** Poor connection to the RPC (Remote Procedure Call) server, which acts as your gateway to the Solana blockchain. **Solution:** 1. **Check Your Current Latency** * Look at the bottom row of the Flash.Trade interface * Your RPC ping time should be below 500ms for optimal trading experience * If ping exceeds 500ms, proceed to change your RPC provider 2. **Change RPC Provider** * Click the **Settings** icon in the top-right corner of the interface * Select **RPC Endpoints** from the dropdown menu * Choose from the available options: * **Triton** - High-performance RPC provider * **Helius** - Alternative reliable RPC option * **Custom RPC** - Use your own RPC endpoint if available * Click **SAVE RPC** * The page will automatically reload within 3 seconds * Verify improved latency at the bottom of the interface ### VPN-Related Connection Issues **Problem:** Positions not loading, interface glitches, or intermittent connectivity problems. **Cause:** VPN services can interfere with RPC communication and cause data synchronization issues. **Solution:** * Temporarily disable your VPN connection * Refresh the Flash.Trade interface * If issues persist, try switching to a different RPC provider as outlined above *** ## Oracle and Pricing Issues ### Unable to Close Positions During High Volatility **Problem:** Cannot close positions during periods of extreme market volatility or high network congestion. **Cause:** During volatile market conditions, Solana's base fees increase significantly, which can cause Pyth price feeds to become stale or unavailable. This prevents normal position closure mechanisms from functioning. **Solution:** 1. **Enable Backup Oracle** * Navigate to **Settings** in the top-right corner * Expand the **PnL Settings** section * Toggle **"Use Backup Oracle"** to the ON position * Click **SAVE** to apply changes 2. **Adjust Slippage Tolerance** * In the same Settings menu, locate **Slippage Tolerance** * Increase the slippage percentage (recommended: 0.8% or higher during volatility) * This accounts for rapid price movements between transaction signing and execution * Click **SAVE** to apply changes {% hint style="warning" %} ## Important Notes: * The backup oracle ensures you can close positions even when primary price feeds are unavailable * Higher slippage tolerance is crucial during volatile periods to prevent transaction failures * These settings can be reverted to normal once market conditions stabilize {% endhint %} *** ## Priority Fee Optimization ### Transaction Failures During Network Congestion **Problem:** Transactions fail to execute or remain pending for extended periods during busy network conditions. **Cause:** Insufficient priority fees during times of high network congestion. **Solution:** 1. **Adjust Priority Fee Settings** * Go to **Settings** → **Priority Fee** * Switch from **DYNAMIC** to **MANUAL** if needed * Increase the fee amount (typical range: 0.001 - 0.01 SOL) * **DYNAMIC** mode automatically adjusts fees based on network conditions (recommended) 2. **Monitor Network Conditions** * Higher priority fees are necessary during periods of high network activity * Consider using DYNAMIC mode for automatic fee optimization *** ## Additional Settings Optimization ### PnL Display Configuration To customize how your profit and loss information is displayed: * **Display PnL With Fees** - Include trading fees in PnL calculations * **Include PnL In Leverage Display** - Show PnL impact on effective leverage * **Use Backup Oracle** - Enable alternative price feeds during disruptions *** ## Best Practices 1. **Regular Settings Review** * Periodically check your RPC latency * Adjust slippage tolerance based on market conditions although 0.8% in most cases will be sufficient. * Keep priority fees at appropriate levels for current network conditions 2. **Network Monitoring** * Be aware of Solana network status during high-traffic periods. Check here [Solana Status](https://status.solana.com/) * Consider increasing priority fees during major market events 3. **Backup Preparations** * Familiarize yourself with backup oracle settings before you need them * Test different RPC providers to identify the best performance for your location *** ## Getting Additional Help If you continue experiencing issues after following this guide: 1. Check [Solana Status](https://status.solana.com/) for network-wide issues 2. Join the Flash.Trade [Discord](https://discord.gg/flashtrade) channel for real-time support 3. Ensure you're using the official interface at [https://flash.trade](https://flash.trade/) {% hint style="danger" %} ## Security Reminder: Only access Flash.Trade through the official URL () to avoid phishing attempts that could compromise your assets. Bookmark [https://flash.trade](https://flash.trade/) to help make sure that you are always on the correct URL. {% endhint %} --- # 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://docs.flash.trade/flash-trade/getting-started/troubleshooting-guide.md?ask= ``` 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.