# Limit Sell
{% hint style="info" %}
**Sell Fee:** The sell fee is taken from the default one in settings.
**Orders expiration –** Expired orders are automatically deleted.
{% endhint %}
{% hint style="danger" %}
**Usage Limits:**
You can have a maximum of 1,000 active orders at any time, with a limit of 10 active orders per configuration
{% endhint %}
***
{% stepper %}
{% step %}
Start a regular selltask by entering the token address.
{% endstep %}
{% step %}
Tap 📈 Limit Orders.
| Button | Action |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Expiry | Set the order expiration time in hours (eg. 6). |
| Sell at Expiry | Make your order trigger at expiry if the price / mcap wasn't matched. |
| Sell Amount | Choose the % to sell. |
| Fee | Set the transaction fee for buying. |
| Tip | Set the buy tip fee to prioritize the inclusion of your transaction in the next block. |
| Slippage | Set the buy slippage percentage. |
| Sell Protection | Toggle MEV protection (enabled/disabled) to prevent your transaction from being sandwiched. The fastest processor is automatically used. |
| High Impact (Expert only) | Allows selling with higher price impact than usual. Useful for large sell orders in low-liquidity pools.
⚠️ Expert users only: using this when it’s not needed can route the sale through suboptimal pools or cause bad slippage.
|
| Dev Sell | Choose whether to automatically buy the specified amount if the Dev sells any of their tokens.
If enabled, the bot will ignore the set profit/loss percentage and only trigger a sale when the Dev sells.
|
| Market Cap | • Choose to create the order based on market cap.
• Enter the target market cap value.
|
| Price | • Choose to create the order based on price.
• Enter the percentage of the current price at which you want to create the order.
|
| Time | Sell after a desired timespan.
Enter the expiry time in:
• 1H = 1 hour
• 30M = 30 minutes
• 1D = 1 day
• 60 = 60 seconds
|
| Trailing | A Trailing Stop Loss moves automatically as the token price increases. The Trailing Value (%) represents the distance between the current price and where the stop loss is set. As the token price rises, the stop loss moves up with it, always maintaining that distance.
If the price drops enough to hit the trailing level, the order triggers and closes the position automatically.
|
| Create Limit Order | Create the limit order. |
| {% endstep %} | |
| {% endstepper %} | |
***
{% stepper %}
{% step %}
### Take Profit
{% hint style="info" %}
To set multiple Take Profits, create separate orders with different market caps/prices and percentages aligned with your goals and strategy.
{% endhint %}
To set a take-profit, enter a market cap or price higher than your entry price. If you prefer to use a percentage, create an Auto Order instead.
{% endstep %}
{% step %}
### Stop Loss
{% hint style="info" %}
To set multiple Stop Loss, create separate orders with different market caps/prices and percentages aligned with your goals and strategy.
{% endhint %}
To set a stop-loss, enter a market cap or price lower than your entry price. For percentage-based stops, use Auto Orders.
{% endstep %}
{% endstepper %}
---
# 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.bloombot.app/solana/solana-bot/limit-orders/limit-sell.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.
