How I Fought Bybit's Partial TP/SL Mode and Got Almost Nowhere — TradingView Automation with Bybit
A few days ago I had what looked like a pretty normal request. A user was trading on Bybit from TradingView and opening several entries in the same direction. He wanted every new entry to keep its own Take Profit and Stop Loss. Not one TP and SL for the whole position, but separate levels for every entry. The first BUY could happen at one price, the next one an hour later at another price, and a…
A user requested to open several entries in the same direction on Bybit from TradingView, with each entry having its own Take Profit and Stop Loss. This is problematic for Bybit as it may treat multiple orders as one growing position, leading to a shared Stop Loss based on the average entry price. The user initially implemented a solution using Bybit's Partial TP/SL mode, creating TP/SL protection only for each new part of the position.
However, Bybit limits the number of TP/SL orders to 20 under Partial mode. When the user tried to open more setups, Bybit refused to create additional Partial TP/SL orders. The user then considered switching to Full TP/SL but realized this would change the original TradingView strategy where each setup should remain independent.
The user discovered that TradingView already knows the TP and SL levels for each entry. Instead of creating a new Partial TP/SL order for each entry, the user proposed a new flow where TradingView opens the position without TP and SL, and when a setup's TP or SL condition is met, TradingView sends a close instruction to Bybit. This approach eliminates the Partial TP/SL order limit while maintaining the individual exits for each TradingView setup.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
