TradingView Pine Script v5 strategy.exit Stop Limit Syntax — What It Really Means

What strategy.exit is really doing here

For a query like tradingview pine script v5 strategy.exit stop limit syntax, the biggest confusion is usually around meaning, not raw syntax. In Pine Script, strategy.exit() is how you define exit orders for an open position. The interesting part is whether you are defining a stop-loss, a take-profit, a trailing behavior, or a bracket that combines both stop and limit levels.

That distinction matters because a lot of traders use the words “stop limit” loosely when they really mean “I want both a stop-loss and a target on the same position.” Those are not the same thing conceptually, and they should not be documented as if they were.

• use stop when you mean the loss-protection price
• use limit when you mean the take-profit price
• do not assume stop + limit means one combined entry order
• always check how the strategy tester is interpreting the exits

The clean pattern most traders should start with

A basic bracket exit is usually the best starting point: one entry, one stop price, one target price. That keeps the logic inspectable before you add partial exits, trailing behavior, or stateful management.

If the simple bracket is unclear, the complicated version will not become clearer later.

//@version=6
strategy("Exit syntax reality check", overlay = true)

if ta.crossover(ta.ema(close, 20), ta.ema(close, 50))
    strategy.entry("L", strategy.long)

if strategy.position_size > 0
    stopPrice  = strategy.position_avg_price * 0.99
    limitPrice = strategy.position_avg_price * 1.02

    // In strategy.exit(), stop + limit creates a stop-loss and take-profit bracket.
    // It is not a single stop-limit entry order.
    strategy.exit("Bracket", "L", stop = stopPrice, limit = limitPrice)

Common mistakes that make the syntax look broken

Many complaints about strategy.exit are really design complaints. The code may compile, but the trader expected behavior the function was never meant to provide. The most common example is expecting a single stop-limit style object when the code is actually defining two separate exit thresholds for a bracket.

• placing exit logic without checking whether the position is open
• mixing percentage thinking with raw price levels carelessly
• treating a target and a stop as if they were one concept
• building the complex version before the simple bracket has been tested

How I check whether the exit logic is trustworthy

I want the exit logic to answer three questions cleanly. When does the trade become invalid? When is profit good enough to take? And does the tester behave the same way the author thinks the code behaves? If those answers are muddy, the exit block is not ready yet.

What to read next

If this topic is part of a bigger TradingView or Pine Script workflow for you, these are the most useful follow-up guides on the site.

• strategy.exit Stop Loss Take Profit
• strategy.exit Stop Limit Example
• Pine Script v6 vs v5

Frequently asked questions