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

Description and use

The article explains how to overcome Bybit’s 20‑Partial TP/SL limit by letting TradingView handle exits, opening positions without TP/SL and sending exit alerts when conditions are met.

Problem

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 execution failures.

Outcome

The hybrid strategy allows unlimited independent TradingView setups without hitting Bybit’s 20‑Partial TP/SL limit, while still providing exchange‑native protection when desired.

Workflow

• 1. TradingView generates an entry signal and calculates TP/SL levels.
• 2. Webhook forwards entry to execution service.
• 3. Execution service opens position on Bybit without TP/SL (Partial mode disabled).
• 4. TradingView monitors price; when TP or SL condition is met, it sends an exit alert via webhook.
• 5. Execution service receives exit alert and sends close order to Bybit for the required size.
• 6. Bybit executes the close order; position size is reduced accordingly. If the exit is not triggered, the position remains open until manually closed.

Evidence

Bybit allows up to 20 TP/SL orders under Partial tpSlMode

Source

TradingView already knows where those exits are. The strategy calculated them in the first place.

Source