TradingView Long and Short Position Alerts: What Fires at Entry, Stop and Target

Since 28 August 2026, you can set one alert on a TradingView long or short position drawing and have it watch all three levels of the plan: entry, stop loss and take profit. The alert notifies you when price reaches the entry, keeps watching, notifies you again when price reaches the stop or the target, and then stops.

The drawing is still a plan on a chart. The alert itself places nothing at your broker, and the drawing's stop does not protect any position. This article explains what the alert does at each level, what happens when you move the drawing, and why this alert type is a poor fit for sending fixed trade instructions to an automated workflow such as PineConnector.

What changed

TradingView announced alerts on long and short position drawings on 28 August 2026 (the post was updated on 31 August 2026)^[1]. Before this, the drawing showed your levels but could not alert on them, so traders copied each level onto a horizontal line and set an alert on every line. Now a single alert covers the whole drawing. TradingView's Help Center explains that one condition covers entry, stop loss and take profit together, so there is nothing to choose between^[2].

To create one, right-click the drawing and select "Add alert on long/short position…", or left-click it and select "Add Alert"^[2]. The announcement also mentions the drawing's floating toolbar^[1]. The alert comes with a pre-filled message, which you can keep or customise^[1]. TradingView's example of the default message is "SWRD, 1m long position, price hits En at 54. Qty: 196. PnL: 3.38."^[2]

Two restrictions from the Help Center matter when you plan around it: the alert only watches price crossing the drawing, and position-drawing alerts cannot be combined into multi-condition alerts^[2].

What the alert does at each level

The Help Center sets out the sequence. When price crosses the entry level, you get one notification and the alert stays active. When price later reaches the take profit or the stop loss, you get one more notification and the alert stops^[2]. The announcement adds that if price is already beyond your entry when you create the alert, it still watches for the exit^[1].

The Help Center's wording, that you are notified "that the position has opened", describes the drawing's plan. The alert itself opens nothing at your broker. A position from this plan exists only if a separate instruction reached the broker and a deal was filled.

Moving the drawing, or editing its levels, changes what the alert watches. TradingView says that moving or editing the drawing restarts the alert with the updated values^[1]. TradingView does not say whether a restarted alert watches the entry again when the original entry had already been reached. If you move a drawing after its entry notification, check the alert's status in the alert manager rather than assuming which stage it is in.

The "Qty" in the message is TradingView's calculation for the drawing, not a broker lot size. Since 27 October 2025 the tools also take a leverage setting, and TradingView sizes the drawing as the smaller of a risk-based quantity and a leverage-based quantity, written as Qty = min(QtyRisk, QtyLvg)^[3]. Your broker's contract size, lot step and margin rules decide what a real order of that size would be.

Eight things that are easy to confuse

TradingView's announcement says the alert tells you the moment "your entry fills"^[1]. In that sentence, "fills" means that price reached the drawing's entry level. The alert itself placed no order. MetaTrader separates three things that happen at the broker: an order is an instruction, a deal is the actual buy or sell that executes it, and a position is the resulting open exposure^[4]. Keeping every stage apart avoids most of the confusion:

1. Drawing level. A price you marked on a TradingView chart. It does not show that any order, stop or target exists.
2. Triggered alert. TradingView saw price cross the level on its own data, recorded in the Alerts log. It does not show that a message was delivered anywhere.
3. Delivered webhook. The alert's message was sent to the URL you entered, shown in the Alerts log's webhook status. It does not show that the receiver understood the message.
4. Processed signal. PineConnector received and read the message, shown in PineConnector's Bridge. It does not show what the broker did.
5. Order accepted. The broker's trade server checked the order request and took it for processing. MetaTrader's help notes that an accepted order can still be executed, cancelled or rejected^[4]. Acceptance is not a fill.
6. Deal filled. The order was executed and a deal appears in the account history, at the broker's price. One order can produce more than one deal^[4].
7. Position open. The deal opened (or changed) a position, visible in MetaTrader's Trade tab with its volume.
8. Stop loss on the position. A stop loss set on that open position at the broker, shown as its S/L. It still does not mean the position will close at exactly that price.

Only the last four exist at your broker. MetaTrader's help describes Stop Loss and Take Profit as executed on the trade server, so they keep working when the platform is off, whereas MetaTrader's own trailing stop runs in the platform^[4]. A stop drawn on a TradingView chart has none of those properties. It is a line that can trigger a notification.

Prices can also differ between the two platforms. A notification says price crossed the level on TradingView's chart data. Your broker quotes its own bid and ask. PineConnector's troubleshooting guide treats a difference between TradingView and broker prices as its own check, and points to the broker's actual symbol and price feed^[6].

Why this alert does not fit a fixed trade instruction

An alert has one message field. This alert fires on two different events, entry and exit, and notifies you each time. Neither TradingView's announcement nor its Help Center guide describes webhook delivery for this alert type^[1][2]. Undocumented is not the same as unavailable, but webhook delivery from this alert type was not tested for this article. TradingView's default message changes with the level that fired, but TradingView does not document a placeholder you can use to tell the two events apart in a message of your own. PineConnector, in turn, acts on the command written in the message, one command per message, in the order License ID, command, symbol, parameters^[5].

Put those together and a fixed instruction goes wrong on the second event. Suppose the message were a buy instruction and it reached PineConnector by webhook. The entry event would send a buy request, and the stop or target event would send the same buy request again, when the plan called for a close. The default message is not an instruction PineConnector can act on either, because it does not follow PineConnector's message structure.

Two more details follow from how the alert is described. When you move the drawing, the alert restarts with the drawing's new values^[1], but a price you typed into the message is plain text, and nothing in TradingView's description says it changes. And because TradingView describes one condition for all three levels^[2], there is no documented way to give the entry and the exits separate messages within this alert type.

For those reasons this article gives no automation recipe for position-drawing alerts. Use them to notify yourself.

If you want the plan executed, design the instruction separately

A plan drawn with this tool can still inform an automated setup, but the instruction has to be built as its own alert, with its own message, for one action. PineConnector's troubleshooting guide asks for one separate alert message per instruction^[6]. Three points apply to any such design:

• Protective levels belong with the entry. PineConnector's syntax can request a stop and target together with the entry, for example with sl_price= and tp_price=. Once a stop loss is actually set on the open position, visible as its S/L in MetaTrader, closing at that level no longer depends on another alert arriving^[4].
• A chart price may not be a valid broker price. PineConnector's reference for sl_price= asks you to check the correct side of entry, the broker's tick size and its minimum stop distance, and warns that a price taken from TradingView can be invalid at the broker^[5].
• Exits need their own design. Closing a position is a different command from opening one. Read the closing commands in the PineConnector Syntax reference before combining entries and exits in one strategy.

None of this was tested for this article. Run any new instruction through PineConnector's demo test workflow and confirm the result in the TradingView Alerts log, the PineConnector Bridge and the broker account, in that order^[7]. At the broker, check the order, the deal and the open position with its S/L separately. The guide to position size, stop loss and take profit explains the sizing and stop methods.

Limitations and common mistakes

• Treating the entry notification as a fill. It means price crossed the drawing's entry level on TradingView. Check your broker account for what actually exists.
• Treating an accepted order as a trade. An order the server accepted can still be cancelled or rejected. Look for the deal and the open position.
• Relying on the drawing's stop. The drawing's stop can notify you. It cannot close a position.
• Reading Qty as lots. TradingView calculates Qty for the drawing from its own inputs^[3]. Broker sizing rules are separate.
• Moving the drawing after the entry notification. The alert restarts with the new values^[1]. Check its status instead of assuming which level it is watching.
• Expecting combined conditions. Position-drawing alerts do not support multi-conditions^[2]. For confirmation logic, see how multi-condition alerts combine.

What to check next

1. Use the position-drawing alert for notifications only, and name it so you can tell it apart from any alert that sends instructions.
2. If the alert's notification settings include a webhook to PineConnector, remove it unless you have a documented, tested reason to keep it.
3. For an automated version of the plan, build one alert per action and include the stop and target with the entry instruction, as described above.
4. Test on a demo account and compare the Alerts log, the Bridge, and at the broker the order, the deal and the position.

TradingView suggests you can set the alert and walk away^[1]. For notifications that is fair, because TradingView runs alerts on its servers. For executed trades on a self-hosted setup, PineConnector's documentation notes that MetaTrader and the EA still have to be running and connected on your computer or VPS^[8]. PineConnector Edge hosts MT5 with the PineConnector EA so that part does not depend on your own machine, with the EA on fixed default settings for now^[9]. See the Edge page for current plans.

Reviewed 23 September 2026. Facts were checked against the linked sources on that date. The examples are illustrative; no alert in this article was run against a trading account.

Related reading

• TradingView updates for alert-based automation: a practical index
• TradingView rectangle alerts: zone conditions vs Greater than and Less than
• TradingView Fibonacci drawing alerts: levels, channels and moving the drawing
• Choosing position size, stop loss and take profit for a PineConnector alert
• TradingView webhook received, but no MT5 trade: a stage-by-stage diagnosis

Sources

1. TradingView Blog – Alerts come to long and short position drawings, published 28 August 2026, updated 31 August 2026, accessed 23 September 2026.
2. TradingView Help Center – How to use long and short position drawing tools, accessed 23 September 2026.
3. TradingView Blog – Leverage support in Long and Short Position tools, published 27 October 2025, accessed 23 September 2026.
4. MetaTrader 5 Help – Trading operations: basic principles, accessed 23 September 2026.
5. PineConnector Docs – PineConnector Syntax, accessed 23 September 2026.
6. PineConnector Docs – Troubleshoot an alert, accessed 23 September 2026.
7. PineConnector Docs – Test your setup, accessed 23 September 2026.
8. PineConnector Docs – Best Practices & Tips, accessed 23 September 2026.
9. PineConnector Docs – Connect your MT5 account (Edge), accessed 23 September 2026.

PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.