> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/manager/pages/tasks/solana/limit-order.md).

# Limit Order

{% hint style="info" %}
Limit orders allow you to set a specific price at which you want to buy or sell a token. Unlike market orders that execute immediately at the current price, limit orders only trigger when the market reaches your desired price or market cap.

***

#### Usage Limit

* You can have a maximum of 1,000 active orders at any time, with a limit of 10 active orders per configuration.
  {% endhint %}

### Limit Order Tab

The Limit Order tab displays all your currently active limit orders across every mode. From this tab, you can monitor your orders and cancel them. To create new limit orders, use the Auto Orders section or Telegram.

| Column                 | Description                                                  |
| ---------------------- | ------------------------------------------------------------ |
| **Type**               | The type of limit order (buy or sell).                       |
| **Token**              | The token the order is placed on.                            |
| **Wallet**             | The wallet assigned to the order.                            |
| **Target**             | The target price or market cap that will trigger the order.  |
| **Amount**             | The amount set for the order.                                |
| **Priority Fee / Tip** | The priority fee and processor tip configured for the order. |
| **Slippage**           | The slippage percentage configured for the order.            |
| **Expiry**             | The expiration time of the order. The column is sortable.    |


---

# 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.bloombot.app/manager/pages/tasks/solana/limit-order.md?ask=<question>&goal=<user_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.