# Limit Orders Limit orders let you set price targets for automatic buy or sell execution. Instead of buying at the current market price, you set the price at which you want to buy or sell, and the order executes automatically when the market reaches that price. *** ## How Limit Orders Work This section details how price-triggered orders operate. ### Buy Limits vs Sell Limits | Order Type | Trigger Condition | Action | | -------------- | ----------------------------------- | ------------------------------------------ | | **Buy Limit** | Price drops to or below your target | Execute a buy at the best available price | | **Sell Limit** | Price rises to or above your target | Execute a sell at the best available price | ### Example: Buy Limit Current price: $100 You set a **buy limit** at $90 When the price drops to $90 or below, your order triggers and executes a market buy. You now own the token at approximately $90 — better than buying at $100. ### Example: Sell Limit Current price: $100 You set a **sell limit** at $150 When the price rises to $150 or above, your order triggers and executes a market sell. You locked in a 50% gain. *** ## Setting a Limit Order ### Step-by-Step 1. **Send `/limits`** — Opens the limit order management panel. 2. **Select "Create Limit Order"** — Starts the configuration flow. 3. **Choose Buy or Sell** — Tap "Buy" or "Sell" depending on your direction. 4. **Enter the token address** — Paste the token's mint address. ARCHONE looks up the symbol and current price. 5. **Set the trigger price** — The price at which your order activates. For buys, this is below current price. For sells, this is above current price. 6. **Set the order amount** — How much to buy or sell: * For buys: Amount in SOL * For sells: Amount in tokens (or percentage of position) 7. **Configure TP/SL (optional)** — You can set take profit and stop loss on the resulting position after the limit order executes. 8. **Confirm** — ARCHONE shows the order summary and asks for confirmation. *** ## Order Expiration By default, limit orders don't expire. They stay active until triggered or manually cancelled. ### Setting Expiration When creating a limit order, you can optionally set an expiration time: * **24 hours** — Order expires tomorrow at the same time * **7 days** — Order expires in a week * **30 days** — Order expires in a month * **No expiration** — Order stays active indefinitely Expired orders are automatically cancelled. *** ## Managing Limit Orders ### Viewing Active Orders Send `/limits` to see all your pending limit orders. For each order, you'll see: * Order type (Buy or Sell) * Token symbol * Trigger price * Order amount * Current market price * Status (Pending, Triggered, Expired, Cancelled) * Time remaining (if expiration set) ### Cancelling an Order Tap on any pending order, then tap **Cancel** to remove it. Cancelled orders don't execute. ### Cancelling All Tap **Cancel All** to remove all pending limit orders at once. *** ## Execution ### How Execution Works 1. **Price check** — The system continuously monitors market prices. 2. **Trigger detection** — When the market price crosses your trigger price (goes below for buys, above for sells), the order activates. 3. **Market execution** — Executes as a market order at the next available Jupiter price. This may be slightly different from your trigger price due to price movement between check and execution. 4. **Confirmation** — You're notified of the execution with the actual fill price and transaction hash. ### Partial Fills If the market price triggers your order but there's insufficient liquidity for the full amount: * Partial fills are supported * The remaining amount stays in the order * The order continues to wait for the next trigger ### Failed Execution If execution fails (insufficient balance, network issue, token inactive): * The order remains active * The system retries on the next price check * No tokens or SOL are deducted until execution succeeds *** ## Interactions With Other Features ### With DCA Limit orders work alongside DCA strategies: * A buy limit order can build a position at a discount while DCA accumulates at regular intervals * A sell limit order above current price can lock in profits on part of your position while DCA continues buying ### With Copy Trading When you copy a trader: * The leader's trades execute in their wallet * Copy trades execute in your wallet at the same time * Any limit orders you have set are independent and don't interact with copy trades ### With TP/SL Limit orders can include TP/SL targets on the resulting position. After execution: * TP/SL monitoring activates immediately * Any configured targets start tracking *** ## Common Use Cases ### "Buy the Dip" You want to buy a token but think it'll drop first. 1. Current price: $100 2. Set a buy limit at $80 3. If the price drops to $80, your order executes 4. If the price never drops to $80, you don't buy ### "Take Profit at Target" You're up 50% on a position and want to secure gains. 1. Current price: $150 (you're in profit) 2. Set a sell limit at $150 (or slightly below to account for fees) 3. If the price stays above $150, your order doesn't trigger 4. If the price drops, you sell at your target ### "Build a Position on Pullback" You want to accumulate more of a token you're already holding. 1. Current price: $100 2. You hold tokens bought at $80 3. Set a buy limit at $90 4. If the price pulls back to $90, you add to your position *** ## Price Types Limit order prices can be entered in two ways: | Price Type | Description | | -------------- | ------------------------------------------------------ | | **USD price** | Absolute dollar value (e.g., $90) | | **Percentage** | Percentage from current price (e.g., -10% = 10% below) | When entering a percentage: * For buys: -10% means buy when price is 10% below current * For sells: +20% means sell when price is 20% above current *** ## Limitations * Limit orders execute as market orders — fill price may differ from trigger price * Very low-liquidity tokens may result in significant slippage on execution * If a token gets delisted or trading pauses, orders may never execute * System must be running for order monitoring — if the bot is offline, orders won't trigger --- # 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/core-features/limit-orders.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.