TradingView Rectangle Alerts: Zone Conditions vs Greater Than and Less Than

TradingView rectangle alerts now answer two different kinds of question. The original conditions, added on 24 November 2025, watch the zone as a whole: price entering, exiting, inside or outside the box. Since 21 August 2026 you can also watch one side of it: Greater than tracks price above the rectangle's upper boundary, and Less than tracks price below its lower boundary.

The practical question is how often each one fires. The names suggest two kinds of condition: crossing a boundary, and being on one side of it. TradingView's Help Center, though, describes its general alert operators as triggering when the value reaches, moves into or out of, or passes a level. How many times a rectangle condition fires for a given trigger frequency is not documented, and every trigger of an alert that feeds PineConnector is a separate message. This article sets out what each condition watches, what each frequency allows, and how to count the triggers on a demo alert.

What changed

TradingView introduced alerts on rectangle drawings on 24 November 2025 (updated 4 December 2025)^[2]. The announcement described three situations: price entering the zone, price exiting it (a breakout or breakdown), and price being inside or outside its boundaries. The Help Center lists the resulting operators as Entering rectangle, Exiting rectangle, Inside rectangle and Outside rectangle^[3].

On 21 August 2026 (updated 31 August 2026) TradingView added a side-specific pair^[1]. It explained the gap it closes: the original conditions watch the zone as a whole, so they could not tell you that price was on the right side of the zone for your setup. The new conditions are:

• Greater than tracks when price is above the rectangle's upper boundary. TradingView suggests it for a support zone, to know price is holding above it.
• Less than tracks when price is below the rectangle's lower boundary. TradingView suggests it for a resistance zone, to know price is still capped below it.

TradingView adds that moving or resizing the rectangle moves the alert level with it^[1]. On 23 September 2026, the Help Center's list of drawing alert operators still showed only the four original rectangle conditions^[3], so the August announcement is the source for the new pair.

What each condition watches: a labelled example

Take an illustrative support zone on EURUSD drawn from 1.0820 to 1.0850, and a price that falls through it. The diagram marks five points along the way and names the condition that describes each one.

1. 1.0880, above the upper boundary: the side Greater than watches. Price is also outside the zone.
2. Price crossing down into the zone: what Entering describes.
3. 1.0835, inside the zone: what Inside describes.
4. Price breaking down through 1.0820 and leaving the zone: what Exiting describes.
5. 1.0810, below the lower boundary: the side Less than watches. Price is also outside the zone.

Two details are easy to miss. Exiting and Outside do not tell you which side price left by: point 4 would look the same as a breakout through the top. Greater than and Less than do, which is the point of the August addition.

The second detail is timing. TradingView publishes no rectangle-specific definition of when each condition triggers, and its wording points both ways. The August post calls the original four "channel conditions" and says Greater than tracks when price "is above" the upper boundary^[1]. The Help Center's general operator list says Inside and Outside channel trigger when the value "moves into or out of" the boundaries^[3]. For Greater than and Less than, it says the value "surpasses or falls below" a level. Those general lines read more like crossings than lasting conditions. Neither source says whether a rectangle alert fires once at the crossing or again while price stays in place, so count the triggers on a demo alert before you connect anything to it.

Which condition answers which question

• Has price come into my zone? Entering rectangle.
• Has price left my zone, either way? Exiting rectangle. TradingView's example is a breakout or breakdown.
• Is price inside the zone? Inside rectangle.
• Is price outside the zone, on either side? Outside rectangle.
• Is price holding above my support zone? Greater than, which tracks price above the upper boundary.
• Is price still capped below my resistance zone? Less than, which tracks price below the lower boundary.

Each answer picks a condition. None of them tells you how many alerts you will get while price stays in or beside the zone. That depends on the trigger frequency and on how TradingView evaluates the condition.

Why the trigger frequency matters

A condition says what to watch. The trigger frequency says how often the alert may fire when that condition is met. TradingView's Help Center defines the options^[5]:

• Once only: the alert is triggered a single time.
• Once per bar: checked on every bar, and triggered whenever the conditions are met, at most once per bar.
• Once per bar close: the same, but only when the bar closes.
• Once per minute or every time: checked every minute, and triggered whenever the conditions are met.

A frequency sets a ceiling, not a count. Once only allows one trigger. Once per bar allows at most one per bar, and only on bars where TradingView treats the condition as met. For rectangle conditions, TradingView does not document whether that means only the bar where price crosses a boundary or every bar price stays inside, outside, above or below.

If Inside keeps counting as met while price sits in the zone, as its name suggests, Once per bar could trigger it on each of those bars. The Help Center's "moves into or out of" wording suggests it may not. The reliable answer is a count: set a test alert on the chart with a plain notification (no webhook), and read the Alerts log while price sits in or beside the zone.

The count matters because of what the message says. For a notification to your phone, repeat pings are an annoyance. For an alert whose message is a trade instruction, each trigger sends the message again. A fixed entry instruction on a condition that keeps firing could become a series of entry requests, one per bar. PineConnector's own setup guide warns about the receiving side of this, and asks you to check the EA's Pyramiding setting so repeated entries do not add positions^[8]. TradingView also caps a regular alert at 15 triggers within a three-minute window and stops the alert when it reaches that limit^[6].

The bar-close choice matters for breakouts as well. With Once per bar, a condition can be met during the bar and trigger before it closes, even if price then returns into the zone. Once per bar close waits for the bar to close, by definition later than the intrabar touch.

Limitations and common mistakes

• A per-bar frequency on an instruction alert. Allow for repeated messages and count them on a demo alert. Use Once only when exactly one instruction is intended. Entering or Exiting on Once per bar can still fire again each time price re-enters or leaves the zone.
• Assuming Exiting means a breakdown. It fires whichever way price leaves. Use Less than or Greater than when the side matters.
• Moving the box and forgetting the message. The alert level follows the rectangle^[1]. Any price you typed into the message, such as a stop, stays as you typed it.
• The rectangle's time span. A rectangle also has left and right edges set by bar position^[4]. TradingView's announcements describe the upper and lower boundaries and do not say whether the box's time span limits the alert. Check this on your chart before relying on a box that ends in the past.
• Alert limits. A rectangle alert counts as a technical alert, because it uses a drawing^[7]. Technical alerts have their own limit on each TradingView plan.

Before a rectangle alert sends instructions: design checks

TradingView's rectangle guide says that when you create the alert you choose the condition, the frequency and a notification method, and can edit the notification message^[4]. It does not describe webhooks for rectangle alerts specifically. That is not the same as saying they are unavailable, but it means nothing here is a tested or documented route to PineConnector, and this article did not test one. If you plan to connect a rectangle alert, check these points first:

1. One instruction per alert. Decide the single action the alert should request. Then use Once only, or confirm on a demo alert that your condition and frequency fire once for that event. PineConnector's troubleshooting guide asks for one separate alert message per instruction^[9].
2. Repeat triggers. The documentation does not tell you how many times your condition and frequency fire while price sits in or beside the zone. Count them on a demo alert, and check the EA's Pyramiding setting on a demo account.
3. Message format. Any message PineConnector reads has to follow the order in the Syntax reference: License ID, command, broker symbol, parameters.
4. Evidence. Use the demo test workflow and compare the TradingView Alerts log, the PineConnector Bridge and the broker account^[10]. Count the triggers as well as checking the first one, and at the broker check the order, the deal and the position separately.

If trades arrive but look wrong, the stage-by-stage diagnosis walks through where the chain stopped.

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 Fibonacci drawing alerts: levels, channels and moving the drawing
• TradingView long and short position alerts: what fires at entry, stop and target
• TradingView alert syntax: format messages for automation
• TradingView webhook received, but no MT5 trade: a stage-by-stage diagnosis

Sources

1. TradingView Blog – Rectangle alerts now support Greater than and Less than conditions, published 21 August 2026, updated 31 August 2026, accessed 23 September 2026.
2. TradingView Blog – Introducing alerts on rectangle drawings, published 24 November 2025, updated 4 December 2025, accessed 23 September 2026.
3. TradingView Help Center – Getting started with technical alerts, accessed 23 September 2026.
4. TradingView Help Center – Rectangle drawing tool, accessed 23 September 2026.
5. TradingView Help Center – Differences between alert frequencies, accessed 23 September 2026.
6. TradingView Help Center – Alert was triggered too often and stopped, accessed 23 September 2026.
7. TradingView Help Center – Alerts separation by type, accessed 23 September 2026.
8. PineConnector Docs – Connect your strategy, accessed 23 September 2026.
9. PineConnector Docs – Troubleshoot an alert, accessed 23 September 2026.
10. PineConnector Docs – Test your setup, 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.