TradingView Partial Exits: Check Your Stop Coverage

A stop price can be correct while its order quantity is wrong. When a TradingView strategy scales out of an NQ or MNQ position, checking the line drawn on the chart is not enough. You also need to know which contracts each exit can close.

This guide explains a specific Pine Script pitfall: separate exit calls can reserve different parts of a position. It then gives you a practical way to check coverage before and after a partial profit target. The examples are hypothetical order plans, not tested strategy results or live executions.

Why can a three-contract stop close only one contract?

TradingView documents that each strategy.exit() call reserves part of the open position. A later call cannot close contracts already reserved by an earlier call. If requested exit quantities exceed available position size, the emulator reduces them. When both quantity parameters are supplied, qty takes precedence over qty_percent. See the official partial and multi-level exit documentation.

Consider one long entry of three MNQ contracts. Your script first requests a target-only exit for two contracts, then a separate stop-only exit for three. The first exit reserves two. Only one remains available for the later stop call. Writing a quantity of three in that second call does not undo the earlier reservation.

The diagnostic question is simple: if price falls to the stop before reaching any target, where are the instructions to close the other two contracts? A plotted line does not answer that question.

Build an exit map before changing settings

Start with one entry and no added positions. Write an intended allocation that accounts for every contract. For example:

• Entry: buy three MNQ contracts at 20,000.

• First portion: two contracts, target 20,050, stop 19,950.

• Second portion: one contract, target 20,100, stop 19,950.

• After the first target: one contract remains, with its own exit instructions.

This plan assigns both a target and a stop to each portion. TradingView's multiple take-profit FAQ describes separate exit brackets and an alternative using an OCA reduce group. Within a bracket, the target and stop are alternatives for the same quantity. They are not two independent quantities to add together.

For the example, two plus one is the intended protected position of three. Do not count two target contracts plus two stop contracts plus one target contract plus one stop contract as six contracts of coverage. That double-counts mutually exclusive instructions.

A useful review sheet has one line per portion: entry identifier, quantity, target, stop, and the condition that changes or cancels it. If you cannot explain a contract's exit path on that sheet, resolve it before judging the strategy's profit curve.

Check the dollars as well as the quantities

CME specifies MNQ at $2 per index point per contract. Using the hypothetical prices above, and assuming exact fills with no costs:

• Stop before either target: three contracts lose 50 points each: 3 × 50 × $2 = $300 loss.

• First target, then the original stop: two contracts gain 50 points, earning $200; the remaining contract loses 50 points, losing $100. Combined result: $100 profit.

• Both targets: the first portion earns $200 and the second earns 100 × $2 = $200. Combined result: $400 profit.

These are arithmetic illustrations, not forecasts. They assume the intended quantities actually exit and that no entry is added. Commissions and adverse fills reduce the results, and the stop price is not a guaranteed execution price. Use the separate commission and slippage guide when adding costs.

If the first target is followed by a stop at the entry price, the gross combined result would instead be $200. That is a different management rule. Do not silently substitute it for the original stop when comparing results; see break-even stop trade-offs.

Test the order sequence, not just the final profit

Use the exit map as a checklist for controlled tests. Save the script version and settings alongside the observations so that a later change does not erase the explanation.

1. Stop first. Find or construct a test where the stop is reached before either target. Confirm that the intended full position closes, and inspect any quantity left open.

2. First target, then stop. Confirm the position decreases from three to one after the target, and then from one to zero after the stop.

3. Both targets. Check the quantities and prices of the two exits. Reconcile the combined dollars to the entry, rather than treating each profitable portion as a separate full-size setup.

4. Ambiguous candle. If one bar touches more than one exit level, flag the fill sequence for review. Follow the same-candle stop and target checks instead of choosing the most favorable path.

5. Changed size. Repeat the quantity review for every permitted entry size. A two-plus-one allocation designed for three contracts is not a complete design for an entry of one, two, or five.

Record expected quantity, observed quantity, remaining position and the explanation for any difference. A passing result means this particular order-path test behaved as intended. It does not validate the strategy's profitability or every possible market condition.

Two stops at one price can produce multiple alerts

The TradingView FAQ also warns that separate exit functions at the same stop level can generate separate order alerts. Any connected execution system must handle that sequence correctly. A strategy's simulated exit, an alert message and a broker-confirmed fill are different records.

Before relying on an integration, test in an appropriate simulation environment: does each message specify the intended portion, does the receiving system close that quantity, and does its remaining position agree with the strategy? Do not assume that “sell” means “flatten everything,” or that a second message is necessarily a duplicate. The exact behavior depends on the receiving system and its configuration.

What to ask if you cannot inspect the script

You can still request a clear explanation from the developer without access to proprietary code:

• How is the initial position divided among exit portions?

• Does every portion have stop coverage before the first target?

• What changes after a partial exit, and what remains unchanged?

• What happens when the entry quantity differs from the default?

• What evidence confirms the remaining position after each exit?

Keep the answers with your test settings. An unexplained leftover contract is an execution-design issue to investigate, not a reason to optimize another indicator parameter.

Bottom line: a partial-exit plan is complete only when every remaining contract has a defined exit path. Check quantities at each stage, reconcile the dollars, and test the alert-to-execution behavior separately. Educational information only; futures trading involves substantial risk.