How I Fought Bybit's Partial TP/SL Mode and Got Almost Nowhere — TradingView Automation with Bybit

Описание и применение

Bybit ограничивает количество частичных TP/SL до 20, что конфликтует с многократными входами в TradingView. Решение: открывать позиции без TP/SL и управлять выходами через TradingView, отправляя закрывающие ордера при достижении условий.

Задача

Bybit limits the number of Partial TP/SL orders to 20, while TradingView strategies can generate many independent entries each with its own TP/SL, causing the execution service to hit the exchange limit.

Результат

Bybit’s 20‑order Partial TP/SL limit was circumvented by moving TP/SL management to TradingView and only sending close orders to Bybit, allowing unlimited independent setups while keeping exchange‑native protection for strategies that need it.

Рабочий процесс

• 1. TradingView generates an entry signal.
• 2. Webhook forwards entry to execution service.
• 3. Execution service places entry on Bybit without TP/SL.
• 4. TradingView calculates TP/SL for the entry and monitors price.
• 5. When TP/SL condition is met, TradingView sends a close alert via webhook.
• 6. Execution service sends close order to Bybit for the required size.

Доказательства

Bybit does not necessarily see those entries the same way. If several orders increase the same position, the exchange can treat them as one growing position.

Источник

110061: Not allowed to have more than 20 TP/SLs under Partial tpSlMode

Источник

Instead of creating another native Partial TP/SL every time a new entry arrives, the entry can be opened without TP and SL. TradingView keeps watching the setup, and when its TP or SL condition is reached it sends another alert telling the execution side to close the required amount.

Источник