# Troubleshooting This section details solutions to common issues you may encounter when using ARCHONE. Work through these steps in order before reaching out for support. *** ## Bot Not Responding **Symptoms:** You send a command but get no reply. ### Quick Checks 1. **Verify you're in the correct bot** — Make sure you're chatting with the official ARCHONE bot 2. **Check your internet connection** — Telegram needs an active connection 3. **Restart the bot** — Send `/start` to re-initialize ### Still Not Working * The bot may be undergoing maintenance — try again in a few minutes * If the bot was working before, it may have restarted — your settings are preserved * Try a different command to narrow down the issue *** ## Trade Failures **Symptoms:** A buy or sell returns an error message. ### Error Codes and Solutions | Error Code | Meaning | How to Fix | | ------------------- | --------------------------------------------------- | ---------------------------------- | | `INSUFFICIENT_SOL` | Not enough SOL for the trade plus network fees | Add more SOL to your wallet | | `SLIPPAGE_EXCEEDED` | Price moved more than your slippage tolerance | Retry with higher slippage setting | | `NO_ROUTE` | Jupiter couldn't find a trading path for this token | Token may be too new or inactive | | `LOW_LIQUIDITY` | Token has less than $5,000 liquidity | Avoid trading this token | | `DAILY_LOSS_LIMIT` | You've hit your daily loss limit | Try again tomorrow | | `TRADING_DISABLED` | Bot is locked with `/lock` | Send `/unlock` | | `TOKEN_INACTIVE` | Token is paused or delisted | Cannot trade this token | | `FAILED` | Generic failure | Retry or try again later | ### How to Retry 1. Wait 10–30 seconds (network congestion may clear) 2. Check your balance is sufficient 3. Try with slightly higher slippage 4. If persistent, the token may have issues *** ## Deposit Not Credited **Symptoms:** You sent SOL to your deposit address but your balance didn't update. ### Timeline Deposits are detected within **30 seconds** of blockchain confirmation. Solana usually confirms in 3–5 seconds, so the total wait is typically under a minute. ### Checklist 1. **Wait 30 seconds** — The next scan cycle may find your deposit 2. **Check Solana confirmation** — Use solscan.io to verify the transaction confirmed 3. **Verify the address** — Ensure you sent to the address shown in `/deposit` (not an old address) 4. **Check you're on Solana** — You must send SOL on the Solana network, not Ethereum or BSC ### Still Not Working * If the transaction shows confirmed on Solana but your balance didn't update, contact support * Include your transaction hash when reaching out *** ## Sniper Not Triggering **Symptoms:** You configured sniper mode but it never bought. ### Common Causes | Cause | Solution | | ------------------------ | ------------------------------------------------------------ | | Token already has a pool | Sniper only catches NEW pools created after you configure it | | Insufficient balance | Ensure you have enough SOL for your buy amount | | Slippage too low | New tokens need 3–5% slippage | | Min liquidity too high | Lower your minimum liquidity filter | | RPC stuck | Try the bot again or check network status | ### How Sniper Works Remember: sniper mode watches for **new** pools. If the token already had a pool when you configured the sniper, it won't trigger. In this case, use a regular `/trade` instead. *** ## Agent Not Trading **Symptoms:** Your agent is active but no trades execute. ### Quick Checklist | Requirement | How to Check | | --------------------- | -------------------------------------------------- | | Agent status = Active | Check the agent dashboard shows "Active" | | SOL balance | Ensure your wallet has SOL for trades and fees | | Mode = Live | Agent must be in Live Mode, not Paper Mode | | AI credits | Check you have sufficient credits for AI reasoning | ### Paper vs Live Mode If your agent is in **Paper Mode**, it simulates trades but doesn't execute real ones. To switch: 1. Send `/agents` 2. Tap on your agent 3. Tap **Mode** 4. Confirm the switch to Live ### No Credits AI reasoning consumes credits. If credits run out, the agent pauses. Replenish credits to resume. *** ## TP/SL Not Triggering **Symptoms:** Your take profit or stop loss didn't execute when expected. ### Requirements for TP/SL * **The bot must be running** — TP/SL monitoring requires an active bot connection * **The trade must have been confirmed** — TP/SL only activates after the buy is confirmed on-chain * **TP/SL must be configured** — Make sure you set TP/SL when placing the trade, or add them after ### Price Calculations TP/SL triggers based on the **entry price**, not the current price. If your entry was $100 and TP is +50%: * TP triggers when price reaches $150 ### TP/SL Percentage The TP/SL percentage is calculated from your **entry price**, not your position size. For example: * Entry: $100 * TP at 50%: Triggers when price = $150 * This applies to each individual trade, not your portfolio *** ## Position Not Showing **Symptoms:** You bought a token but it doesn't appear in your portfolio. ### Possible Reasons | Reason | How to Fix | | ------------------- | ------------------------------------------ | | Trade failed | Check your trade history for failed trades | | Wrong token address | Verify you traded the correct token | | Sync delay | Wait a few seconds and refresh portfolio | | Different wallet | Ensure you're in the correct bot account | ### How to Check Send `/portfolio` and tap **Refresh** to update. If the position still doesn't appear, check your trade history in the portfolio section. *** ## Copy Trading Not Working **Symptoms:** Your leader made a trade but no copy trade appeared. ### Checklist | Check | Fix | | ------------------- | ---------------------------------------------------- | | Following status | Make sure you're not paused on that leader | | Your balance | You need SOL to execute copy trades | | Copy amount | Your copy amount may be below the minimum (0.01 SOL) | | Leader's trade size | If leader traded < 0.01 SOL, no copy triggers | ### How Copy Works Copy trades execute after the leader's trade completes. There's typically a few seconds of latency. If your leader traded and you didn't receive a copy, check: 1. You're still following them 2. You have sufficient balance 3. The leader's trade was at least 0.01 SOL *** ## DCA Not Executing **Symptoms:** Your DCA is configured but no buys are happening. ### Possible Reasons | Reason | Solution | | ---------------------- | --------------------------------------------- | | Insufficient balance | DCA can't buy if you don't have enough SOL | | DCA is paused | Resume it from `/dca` | | All intervals complete | DCA finishes when all intervals have executed | | Bot offline | DCA requires the bot to be running | ### DCA Completion A DCA with 10 intervals completes after all 10 buys execute. Once complete, it shows as "Completed" and no longer executes. *** ## Limit Order Not Triggering **Symptoms:** Your limit order's trigger price was hit but the order didn't execute. ### Possible Reasons | Reason | Solution | | -------------------- | ------------------------------------------- | | Insufficient balance | You need SOL for buys, tokens for sells | | Partial fill | Check if some of the order filled | | Order expired | Cancel and recreate if it had an expiration | | Price moved too fast | Market order filled at a different price | ### Limit vs Market Orders Limit orders trigger **market orders** when the price condition is met. The actual execution price may differ slightly from the trigger price due to price movement between check and execution. *** ## General Tips ### Keep the Bot Active ARCHONE works best when you stay connected. If you open the bot rarely, you might miss: * TP/SL notifications * Copy trade alerts * Agent decision updates Open the bot every few hours to stay current. ### Use Built-In Safeguards * Set **stop losses** to protect against losses * Use **small position sizes** — don't bet everything on one trade * Start with **Paper Mode** for agents before going live * Use `/lock` when away ### Stay Informed * Follow official ARCHONE channels for updates * Check `/help` if you're unsure what a command does * Review your portfolio regularly *** ## Still Need Help? If you've tried these troubleshooting steps and still have issues: 1. **Document the problem** — Note the exact error message, time it occurred, and what you were doing 2. **Check our status page** — Service disruptions are posted there 3. **Contact support** — Through official channels with your documentation Include in your message: * The command you were trying to use * The exact error message * What you've already tried * When the issue started --- # 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.archone.trade/reference/troubleshooting.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.