One symbol
Use the same dated futures contract in every condition. Multiple conditions can check different timeframes.

Synthetic MES 5-minute candles. Times are bar closes in ET.
At 9:45 the close is above 6,010.00 but assumed RSI is 66, above the filter ceiling. At 9:50 the close is still above the level and assumed RSI is 64.5. Both states now hold, even though the crossing happened on the earlier close.
Use the same dated futures contract in every condition. Multiple conditions can check different timeframes.
One condition passing on a previous bar does not establish that both pass later.
A crossing marks the transition. Greater Than checks whether the value is above the level at evaluation.
The two conditions are close greater than 6,010.00 and RSI less than 65. The RSI values shown at the four decision times are illustrative inputs that use more history than the chart shows.
Open your dated MES contract on a standard five-minute chart. Add Relative Strength Index and a simple moving average with Length 1, Source Close and Offset 0. That moving average’s value matches the close and gives the alert an interval-dependent price plot.
Open Create alert. Select the one-period moving average plot, choose Greater Than and enter 6,010.00. Select Add condition, set RSI to Less Than 65 and confirm Add. Check that both condition previews use the intended symbol and five-minute interval.
Select Once per bar close where offered for the technical alert. Name it with the symbol and both tests, then enable the intended notification. The numbers are examples to study. An existing alert can keep its previous indicator configuration, so check the saved version after edits.
TradingView lists this feature for Plus and above. One multi-condition alert counts toward the technical-alert limit. TradingView says the conditions must share a symbol, and that watchlist alerts, strategies, and scripts with alert() calls are unsupported. There are also restrictions for older Pine scripts using alertcondition().
When conditions use different timeframes, TradingView bases alert frequency on the smallest timeframe. Use the saved timeframe of each condition and the Alerts Log to check how your actual configuration behaves. This exercise keeps them both at five minutes so each row has a single evaluation time.
This separate Pine example checks the five-minute close and the last completed 15-minute close against 6,010.00. At 9:50 ET, the five-minute candle closes at 6,011.00. The current 15-minute candle is still forming and eventually closes at 6,009.00 at 10:00. The last completed 15-minute candle available at 9:50 closed at 6,008.75, so the filter fails.
The 15-minute candle ending at 10:15 closes at 6,012.00. The script uses that value from the start of the next 15-minute interval. The first five-minute candle in that interval closes at 10:20, at 6,011.25. Both conditions are now true. On TradingView, the five-minute bar can be labeled 10:15 because that is when it opens. Log its 10:20 evaluation and the 10:15 close of the higher-timeframe candle separately.
Add the script to a standard five-minute chart, then create a technical alert using Both closes above level and Once per bar close. Data Window shows the 15-minute value the script uses. The [1] offset reads the preceding 15-minute candle. Combined with lookahead_on, it makes that completed value available from the start of the next interval. Keep the offset. A chart-bar close alone leaves any developing higher-timeframe input subject to change. Each qualifying five-minute close can trigger under this state-based rule.
Synthetic MES 5-minute candles. Times are bar closes in ET.
The 9:50 close is above 6,010 while its 15-minute candle is still forming. The 15-minute candle ending at 10:00 closes below the level. The candle ending at 10:15 closes above. At 10:20 both conditions pass for the first time in the example.
//@version=6
indicator("MES alert with a confirmed 15-minute filter", overlay = true)
if timeframe.in_seconds() != timeframe.in_seconds("5")
runtime.error("Use a five-minute chart for this example.")
float level = input.float(6010.0, "Price level", step = 0.25)
float confirmedClose = request.security(syminfo.tickerid, "15", close[1], lookahead = barmerge.lookahead_on)
bool bothPass = barstate.isconfirmed and close > level and confirmedClose > level
plot(confirmedClose, "Confirmed 15-minute close", display = display.data_window)
alertcondition(bothPass, "Both closes above level", "Five-minute close and confirmed 15-minute close are above the level.")Platform details on this page were checked against these official resources.
Check the stop reason and the trigger timestamps before resuming or replacing it.
Compare the web Alerts Log time with the saved delivery schedule and your device settings.
Match the Alerts Log status to the receiving app’s history.
Check the range and its confirmation time before setting a price condition.
Verify the session anchor and chart data before creating an indicator condition.
The built-in multi-condition alert requires all its configured conditions to be true together. If you need independent reminders, set up separate alerts.
The other condition may have been false on the crossing. Compare the conditions at the same close. If your intent is to consider price above a level while a filter catches up, use a state condition such as Greater Than.
Futures trading contains substantial risk and is not suitable for every investor. TradeReign is a trading-discipline and rule-enforcement application. It does not provide trading advice, trade signals, investment recommendations, or performance guarantees.
TradeReign is not a broker-dealer, futures commission merchant, or investment advisor.
Futures trading contains substantial risk and is not for every investor. An investor could potentially lose all or more than the initial investment. Only risk capital - money that can be lost without jeopardizing financial security or lifestyle - should be used for trading. Past performance is not necessarily indicative of future results.