When using the Take-Profit/Stop-Loss (TP/SL) feature on Toobit, some users may encounter situations where the trigger price is reached, but the order fails to execute. This is usually due to how TP/SL orders work, and factors such as order type selection, market volatility, or account conditions.
On Toobit, a TP/SL order is only submitted to the market after reaching the trigger price. You can choose from two trigger types - Last Price and Mark Price - and three order types: Market, Limit, and Guaranteed Take-Profit (GTD). Below are some of the most common reasons why a TP/SL order may fail to execute, along with practical examples.
1.Trigger Price Not Reached
TP/SL orders are created as "trigger orders" and are not immediately submitted to the order book. Only when the trigger price (based on either the Last Price or Mark Price) is reached will the system submit the order to the market using the preset order price.
Example: User A holds a long BTC futures position and sets a take-profit with a trigger price of 100,000 USDT and an order price of 100,100 USDT.
Once the Last Price of BTC reaches 100,000 USDT, the system will place a limit sell order at 100,100 USDT. Whether it gets filled depends on the market depth at that moment.
2.Limit Orders May Not Fill or May Partially Fill
Toobit supports the following TP/SL order types:
- Market Orders: Upon being triggered, the system will place the order at the best available market price, enabling faster execution.
- Limit Orders: Upon being triggered, the system will place a limit order at your specified price — that is, the highest buy price or lowest sell price you are willing to accept.
- Guaranteed TP Orders: GTD orders ensure that your take-profit order is only executed at a price equal to or better than the trigger price, effectively protecting your profits from slippage. GTD orders are free of charge and function as limit TP orders. However, like regular limit orders, they do not guarantee execution, even if the trigger price is reached.
Example: User B holds a BTC long position with an average entry of 100,500 USDT, and sets a stop-loss with both the trigger and limit price set at 100,450 USDT.
When the last price hits 100,450, the system will place a sell limit order at that price. However, in fast-moving or volatile markets, the price may drop quickly below 100,450, making it less likely that the order will get filled, or only partially filled.
To improve the chance of execution, it's often better to set your limit price slightly more conservative than the trigger. For instance, with a trigger at 100,450 USDT, consider setting the limit at 100,400 USDT to increase the likelihood that your order is filled once triggered.
3.Triggered ≠ Executed
TP/SL follows a "trigger + limit order" model. Even if triggered, the actual order may not execute if there is a large gap between the limit price and the market price at the time.
Example:
User C holds a short ETH position and sets a take-profit trigger at 3,000 USDT, with a limit price of 2,950 USDT.
When the price reaches 3,000 USDT, the limit buy order is placed. However, if the best ask price is 2,900 USDT, the order will remain unfilled or be partially filled until a matching order is available.
4.Account or System Conditions Prevent Order Submission
Even if the trigger condition is met, your order may fail to enter the market due to the following reasons:
- Order price exceeds platform limits
- Insufficient position (already partially closed or occupied)
- Insufficient margin
- The contract is temporarily suspended
- System maintenance or network delays
Example: User D sets a stop-loss with a trigger price of 100,050 USDT and a limit price of 100,000 USDT.
At the time of trigger, the account has insufficient margin, resulting in order submission failure.
5.Matching Engine Priority Affects Order Execution
Toobit's matching engine follows the price-time priority principle. Once your TP/SL order is triggered and submitted, it enters the market like any other order. If many orders are already queued at the same price level, your order will need to wait for its turn, which may result in delayed or partial execution.
Example: User E sets a BTC take-profit trigger at 101,000 USDT with a limited order price of 100,800 USDT.
Once the trigger condition is reached, the system submits the order. However, due to a large volume of existing sell orders at 100,800 USDT placed by other users, the TP order will be queued and may experience delayed or partial execution.
6.How to Improve the Execution Rate of TP/SL Orders
To enhance the execution efficiency of your TP/SL orders, we recommend the following:
- Set a reasonable spread between the trigger price and the limit price (e.g., trigger: 100,500 USDT, limit: 100,450 USDT).
- Use market orders or adopt a wider limit price range in highly volatile markets.
- Ensure a sufficient margin and available position in your account.
- Review market depth and select price levels with better liquidity.
- Utilize Toobit's strategy tools for automated TP/SL execution to reduce manual errors.
We're always here to help. If you have any questions or feedback about this feature, please don't hesitate to reach out to our team through our dedicated Support Center.
Thank you for your trust and support.
Toobit Team
2025-07-15
Find us:
X: https://x.com/Toobit_official
Telegram: https://t.me/Toobit_EN
Discord: https://discord.com/invite/vvxTuGTz
YouTube: https://www.youtube.com/@Toobit_official
Reddit: https://www.reddit.com/r/toobit/
Facebook: https://www.facebook.com/toobitofficial
Medium: https://medium.com/toobit-exchange
Toobit reserves the right to modify or cancel this announcement at any time and for any reason without prior notice.
Risk Warning: The prices of digital assets may fluctuate significantly. The value of your investment may increase or decrease, and you may even lose the entire amount invested. You are solely responsible for your investment decisions, and Toobit is not liable for any losses that may occur due to the use of margin trading. This information should not be considered financial or investment advice. Please refer to our Terms of Use and Risk Disclosure for more details.