> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/trading/limit-orders.md). # Limit Orders **Set the price first — the trade only fires when the market reaches it.** Limit is the second order mode in the GraphDex trading panel. Instead of executing at the current market level, the order parks at a price (or a condition) you choose and fills only once the market touches it. That gives you control over entries on volatile rallies and exits on take-profit / stop-loss plans. Use Limit when you want a defined cost basis, a multi-stage exit ladder, or an order that waits while you sleep. {% hint style="success" %} **Compare it to a market fill first** If you've only used immediate execution so far, see [Market Orders](/graphdex-docs/trading/market-orders.md) before placing your first limit. {% endhint %} ## What Limit Buys You Limit lives inside the same Buy / Sell / Settings panel as Market, with one switch — `Limit` instead of `Market`. The difference is in how the engine treats your price. * **Defined entry.** The order rests until the market trades into your level — no slippage from spike candles. * **Planned exits.** Stack multiple sells at TP1 / TP2 / TP3 ladders or a single hard stop. * **No babysitting.** Active orders show up in the My Orders tab until they fill, error, or you cancel. ## Anatomy of the Limit Panel When you switch to Limit, the panel exposes the same controls as Market plus your target price. The amount input, balance readout, and execution settings (Slippage, Priority Fee, Validator Bribe) work exactly the same way they do on a market order. * Toggle between **Buy** and **Sell** — the same control as Market. * Enter the price or condition you want the order to wait at. * Set amount in SOL (for buys) or percentage of position (for sells). * Confirm Slippage, Priority Fee, and Validator Bribe in the Settings tab. * Submit; the order appears in **My Orders → Active** until it fills. The exact list of fields can shift with the selected token, account state, and product version. Always glance at the panel before clicking submit. ## Before You Place One Limit orders are only as good as the context behind them. A quick checklist: * Confirm direction — Buy or Sell. * Review current liquidity and market cap on the [token page](/graphdex-docs/trading/token-page.md). * Scan recent transaction activity on the same page. * Decide the price (or condition) you actually want. * Re-check Slippage, Priority Fee, Validator Bribe. * After submission, find the order under My Orders and verify status. ## Watching Your Orders The **My Orders** tab is where active and historical limit orders live. The current columns: * **Status** — Active, Completed, Error. * **Date** — when the order was placed. * **Price** — your target. * **Token / Type / Direction** — what the order is doing. * **Instrument** — Limit or Market. * **Actions** — cancel, edit, or replicate. If nothing has filled yet, you'll see the status stay on `Active` until the market hits your level. ## Limit-Order Risks A limit order is a promise to wait — not a guarantee to execute. Plan for the case where it never fills. * **No fill on rallies.** If the market never trades through your level, the order stays open indefinitely. * **Liquidity gaps.** Thin books can leave only part of your size filled. * **Wallet / network errors.** Same failure modes as market orders — a stuck transaction or insufficient gas can move an order to `Error`. * **Execution conditions.** Some pools require min-out, slippage, or routing parameters; check the order details when an Error appears. For a deeper look at why fast-execution paths can fail, see [Risk of Fast Execution Settings](/graphdex-docs/trading/risk-of-fast-execution-settings.md) and [Execution Risks](/graphdex-docs/trading/execution-risks.md). ## More to Explore
Cover image
Market OrdersThe immediate-fill counterpart to Limit./files/PvwZariSc5lrxmA3uidW
Orders and HistoryTrack every order you've ever placed./files/PvwZariSc5lrxmA3uidW
Presets & Quick SuggestionsSave your favourite limit setup./files/PvwZariSc5lrxmA3uidW
{% hint style="info" %} Heading into a busy session? Lock your defaults in [Presets and Quick Suggestions](/graphdex-docs/trading/presets-and-quick-suggestions.md) so every new limit order starts from a tuned baseline. {% endhint %} ## FAQs
Can I edit a limit order after it's placed? Open the order in My Orders → Active and use the Actions column. Some edits cancel the original and replace it with a fresh order; the panel confirms before submitting.
How long does a limit order stay active? Until it fills, errors, or you cancel it. There is no automatic expiry — review the Active list periodically.
Why is my order stuck in Active? The market has not yet traded into your price. Check the token's current price vs. your target; consider editing the limit if conditions have shifted.
What's the difference between Limit and Market? A market order executes immediately at the current price; a limit order waits for the price you set. Limit gives more control; market gives speed.
Can a partial fill happen? Yes — in low-liquidity pools, only part of your size may execute. The remainder either stays Active or moves to Error depending on configuration.
--- # 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://graphdex-1.gitbook.io/graphdex-docs/trading/limit-orders.md?ask=&goal= ``` `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.