TradingView Multi-Condition Alerts: Rules and Limits

A TradingView multi-condition alert combines up to five conditions into one alert that triggers only when all of them are true at the same time. TradingView introduced the feature on 23 October 2025. Every condition must use the same symbol, conditions can use different timeframes, and the alert's frequency follows the smallest timeframe you select. It needs TradingView's Plus plan or higher, and it cannot be used for watchlist alerts or with scripts that send alerts through alert().

For an alert that sends instructions to PineConnector, a multi-condition alert is still one alert with one message. It can make an entry signal more selective without code. It does not know whether you already hold a position, it does not create exits, and it does not size or protect the trade. This guide explains how the conditions combine, the restrictions that shape what you can build, and what a complete automated setup still needs.

Illustration of five numbered condition boxes joining into a single AND node that sends one signal onward.

What changed

TradingView announced multi-condition alerts on 23 October 2025 (updated on 24 October 2025)^[1]. The announcement notes that before this, confirmation logic such as a price touch, an RSI level and a moving-average crossover lining up could only be built in code. Now you open the alert dialog, click Add condition and combine up to five conditions, including price, drawings and indicators. Each added condition is listed as a button showing a short preview, and you can edit or remove any of them^[1]^[2].

How the conditions combine

The logic is AND, never OR. TradingView's Help Center says the alert "will only trigger when all conditions are met simultaneously"^[2]. Two rules follow from the documentation:

One symbol. "All conditions must use the same symbol." You cannot filter a EURUSD entry with a condition on another instrument in the same alert.
Mixed timeframes, one cadence. You can mix timeframes. The alert fires once every condition is true on its own interval, and how often it can fire is set by the smallest timeframe you used^[2].

A worked example makes the timing concrete. Condition A is RSI(14) on the 1-hour chart less than 30. Condition B is price crossing up through a level on the 5-minute chart. The smallest timeframe is 5 minutes, so the 5-minute bars set how often the alert can fire. If Less than counts as met whenever the hourly RSI reading is below 30, the alert fires on a check where price crosses up through the level during that period. A crossing while the hourly RSI is above 30 does nothing. That reading of Less than is ours; the next section shows TradingView's own wording and what it leaves open.

Illustrative diagram with three lanes. Condition A, hourly RSI below 30, is drawn as false, then true, then false. Condition B, a 5-minute price crossing, happens three times. The alert fires only at the crossing that falls inside the period when condition A is drawn as true. — Illustrative diagram. The combination rules come from TradingView's Help Center; the example conditions, and drawing Less than as true while RSI is below 30, are ours.

TradingView does not say which hourly RSI value the 5-minute check reads while the hour is still forming: the developing bar or the last closed one. Before relying on an alert like this, compare a few entries in the Alerts log with the chart at the same times.

Choosing conditions that can line up

TradingView's Help Center describes each operator by what makes it trigger^[11]:

Crossing, Crossing Up, Crossing Down: the value reaches a level, from either direction or from a specific one.
Greater than, Less than: the value "surpasses or falls below" a level.
Entering Channel, Exiting Channel: the value "reaches a channel's boundaries from a certain direction".
Inside Channel, Outside Channel: the value "moves into or out of" the channel's boundaries.

None of these descriptions says that Greater than, Less than, Inside Channel or Outside Channel stays met on every check while the value remains on one side of the level or channel. TradingView also does not document how often each operator fires under a given trigger frequency. The following is our reasoning from TradingView's all-true-at-once rule, not a TradingView statement:

One crossing plus filters, such as price crossing up a level while RSI is less than 30. A crossing is tied to the check where the value reaches the level, so it is the natural candidate to set the timing. Whether the RSI filter is met on that check when RSI has been below 30 for hours, or only on the check where it drops below 30, is the undocumented point above.
No crossing at all, such as price greater than the 200 EMA while RSI is greater than 50. How often a combination like this fires is not documented, so do not assume either a single trigger or one on every bar.
Two crossings, such as two different Crossing conditions. Both have to happen on the same check, which can be rare, so the alert may seldom or never fire.

Trigger frequency matters as much as the conditions. In TradingView's definitions, Once per bar checks every bar and triggers at most once per bar whenever the conditions are met, and Once per bar close does the same but waits for the bar to close^[4]. Those definitions cap triggers at one per bar; they do not say on which bars a given operator counts as met. With mixed timeframes, we read the bar as the bar of the smallest timeframe, because that timeframe sets the frequency. Before relying on any combination, run it as a demo alert and count its triggers in the Alerts log over several sessions.

Restrictions that shape what you can build

TradingView's Plus plan or higher. TradingView says the feature is "Available with the Plus plan and above"^[2], and on 23 September 2026 its pricing page showed it unavailable on Basic and Essential^[6]. This is TradingView's Plus plan, not PineConnector Plus.
One technical alert. Five conditions use one slot of your technical alert limit, because TradingView classes an alert with multiple conditions as technical^[5].
Up to five conditions, one symbol. Cross-instrument filters need Pine Script instead.
Not for watchlist alerts. TradingView rules this out^[1], so each symbol needs its own multi-condition alert.
Not with alert() scripts or strategies. The Help Center excludes strategies and scripts that use the alert() function^[2]. A script that builds its own PineConnector message with alert() stays a single-condition alert.
Not with pre-v4 alertcondition() scripts. Scripts written in Pine versions earlier than 4 that use alertcondition() are not supported^[2].
Not on long/short position drawings. Position-drawing alerts do not support multiple conditions^[3].

A condition is not a trading system

A multi-condition alert answers one question: are all these things true right now? An automated trade needs answers to several more. The table shows which ones the alert covers.

A trade also needs	From this alert?	Where it comes from
An entry moment	Yes	The conditions and trigger frequency
A direction and instruction	Only your text	One message per alert
Awareness of an open position	No	Your exit design and EA settings
An exit	No	A separate alert, or a stop and target
Position size and risk	No	Explicit message parameters

Three of those rows need a word more:

Direction. A long and a short setup need two alerts, each with its own message.
Open positions. The alert does not know you already hold a position. If it triggers again while you do, it sends the same entry again, and TradingView does not document how often a given combination repeats. PineConnector's no-code guide asks you to check the EA's Pyramiding setting so that repeated entries do not add positions^[7].
Exits. A stop loss and take profit can be requested with the entry. They protect a position only once three separate things have happened: the broker accepted the order, a deal filled it, and the levels were set on the resulting position. MetaTrader's help describes Stop Loss and Take Profit as executed on the trade server^[10]. Size and stop units belong in explicit parameters such as vol_lots= and sl_pips=^[8].

Multi-condition alerts and PineConnector: what is and is not established

TradingView neither documents a webhook restriction for multi-condition alerts nor describes webhook use for them specifically. That silence is not evidence either way: it does not show that webhooks work with this alert type, and it does not show that they are unsupported. This article did not test a multi-condition alert with PineConnector, so it gives no setup recipe for one.

What is documented applies to any PineConnector instruction. A message follows the structure LicenseID,Command,Symbol,Parameters, with one command and one symbol per message^[8], and the Syntax reference defines each command and parameter. If you try one on demo, decide the trigger frequency with the repeated-entry question above in mind, and follow PineConnector's demo test workflow before anything reaches a live account.

Limitations and common mistakes

Expecting OR logic. There is no "any of these" option in a multi-condition alert. Each alternative needs its own alert.
Combining two crossings. Two crossings on the same check are uncommon, so the alert may stay silent.
Assuming how often it fires. TradingView does not document how often each operator fires under a given frequency, and that includes Greater than, Less than, Inside Channel and Outside Channel. Count the triggers of a demo alert before it sends anything to an account.
Adding conditions from another symbol. All conditions must use one symbol.
Converting a script alert. A script that uses alert() cannot join a multi-condition alert. Keep its logic in the script.
Reading the trigger as a fill. An entry in the Alerts log shows that TradingView triggered. A signal received by PineConnector, an order accepted by the broker, a filled deal and an open position are separate later facts; PineConnector's docs put it plainly: "A received alert is not proof of a broker fill"^[7].

What to check next

List the conditions and note which one sets the timing. A single crossing is the usual candidate; two crossings rarely line up.
Note the smallest timeframe, since it sets the cadence, and choose the trigger frequency deliberately.
Run the alert as a demo alert and count its triggers in the Alerts log over several sessions, since TradingView does not document how often each operator fires for a given frequency.
Decide how the position closes: a separate exit alert, or a stop and target sent with the entry.
If the alert will carry a PineConnector instruction, check the message against the Syntax reference: explicit size and stop units and the exact broker symbol.
Follow PineConnector's demo test workflow and compare, for the same trigger, the TradingView Alerts log, PineConnector's Bridge, and the broker account's orders, deals and positions^[9].

Reviewed 23 September 2026. Facts were checked against the linked sources on that date. The conditions and timings in this article are illustrative; no multi-condition alert was run against a trading account or sent to PineConnector for it.

Sources

TradingView Blog – Introducing multi-condition alerts, published 23 October 2025, updated 24 October 2025, accessed 23 September 2026.
TradingView Help Center – Multi-condition alerts, accessed 23 September 2026.
TradingView Help Center – How to use long and short position drawing tools, accessed 23 September 2026.
TradingView Help Center – Differences between alert frequencies, accessed 23 September 2026.
TradingView Help Center – Alerts separation by type, accessed 23 September 2026.
TradingView – Pricing and plan comparison, accessed 23 September 2026.
PineConnector Docs – Connect your strategy, accessed 23 September 2026.
PineConnector Docs – PineConnector Syntax, accessed 23 September 2026.
PineConnector Docs – Test your setup, accessed 23 September 2026.
MetaTrader 5 Help – Trading operations: basic principles, accessed 23 September 2026.
TradingView Help Center – Getting started with technical alerts, 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.

Item added to your cart

TradingView Multi-Condition Alerts: How the Conditions Combine, and What They Don't Replace