Price alert
Uses updates for the chosen symbol and level. A change in chart interval does not change the price condition.

Synthetic MES 5-minute candles. Times are bar closes in ET.
Marker 1 trades above 6,010.00 and closes back below. A price crossing can register there. Marker 2 closes above 6,010.00, which meets the close-based crossing in this example.
Uses updates for the chosen symbol and level. A change in chart interval does not change the price condition.
Use an interval-dependent condition and choose Once per bar close.
Check the alert history before diagnosing why a message did not arrive.
Find the exact alert name and symbol around the expected time. Keep the chart, log and device time zones aligned when comparing timestamps.
In Supercharts, open the dated contract you want to monitor and verify the exchange and expiry. Choose Create alert on the toolbar. In Condition, choose Price. Set the level and direction. Crossing up is for an approach from below. Crossing down is for an approach from above.
Choose Only Once for a one-time reminder or Every Time for a recurring price alert. Review expiration and the delivery method. Use a name that includes the contract, level, and direction so you can recognize it in the Alerts panel later.
In the hypothetical MES example, the first 15 minutes after 9:30 ET set a high of 6,010.00. The 9:50 candle trades to 6,011.00 and closes at 6,009.75. A price alert waiting for a crossing from below can fire during that bar. That candle finishes inside the range.
Select the interval you want to review, such as five minutes. Draw a horizontal line at 6,010.00 and create an alert on that drawing. Check that the drawing is selected in Condition. Choose the crossing direction and Once per bar close in Trigger.
With the five-minute close-based crossing in the example, the 9:50 candle ends below the line and does not qualify. The 9:55 candle closes at 6,011.00, above the line, with the previous close below it. The chart labels the difference between those two events.
If Once per bar close is missing, check whether Condition is set to Price. TradingView offers Only Once and Every Time on ordinary price alerts. Drawings and indicators can use interval-dependent frequencies. If you change the underlying indicator settings, review the saved alert and recreate it with the new settings if needed.
TradingView can wait for the first trade of the next bar before it confirms the previous bar closed. In the hypothetical chart above, the 9:55 candle closes above 6,010.00. If the first trade of the next candle arrives at 9:55:07 a.m. ET, the alert can be evaluated after that trade. The scheduled 9:55 close and the Alerts Log time can differ.
TradingView says that if no new trades arrive, such as after a session closes, its server can close the final bar one minute after its scheduled end. Compare the chart interval, exchange session, and the Alerts Log in the same time zone. If the log shows an event at 9:55:07 but your phone displays it at 9:55:25 in this example, those observations separate the trigger delay from the later notification.
If a Pine indicator alert still follows old inputs, check the saved alert. When TradingView creates a script alert it stores a server-side copy of the script, inputs, and chart context. After a rollover, interval change, or script edit, verify the dated contract and exact condition when creating a replacement. Retire the old alert once the replacement is configured so you can identify which one fired.
Create a separately named, notification-only alert using the five-minute horizontal-line condition above. Paste the sample into the alert’s Message field. When the alert fires, check its message in Alerts Log. The fields record the symbol, interval, bar time, trigger time, and the price reported by the bar.
Apply the fictional chart above to November 20, 2026. The 9:55 a.m. ET close comes from the bar that started at 9:50. The bar time placeholder reports 14:50:00 UTC. If the trigger is 9:55:07 a.m. ET, the trigger time reports 14:55:07 UTC. The difference from bar start is five minutes and seven seconds. The trigger is seven seconds after the scheduled close. Record phone delivery time separately if you are testing notifications.
With an ordinary price alert, the interval placeholder can show 1 even if the chart displays five-minute bars. TradingView calculates ordinary price alerts on one-minute bars. For an interval-dependent drawing alert, check the saved condition and interval before deciding the message is wrong. Compare the ticker in the message with your intended futures expiry after rollover.
Symbol {{exchange}}:{{ticker}}
Interval {{interval}}
Bar start (UTC) {{time}}
Fired (UTC) {{timenow}}
Bar close value {{close}}First check whether the alert listens for a script signal or an order fill. A strategy can call alert() when a condition is met. An order-fill alert fires when TradingView’s broker emulator fills a simulated order. In the alert’s Message field, {{strategy.order.price}} reports that simulated fill price.
In the fictional five-minute MES chart, a strategy submits a market buy when the 9:55 a.m. ET candle closes at 6,001.00. With default next-tick execution and zero modeled slippage, the emulator fills at the next bar’s open of 6,002.25. The chart labels that second candle by its 10:00 close. On TradingView it can be stamped 9:55, its opening time. The five-tick difference occurred between the signal price and the modeled fill.
If an actual broker execution report for the same intended buy later shows 6,002.50, that is one tick above the simulated fill. Check the exact account, dated contract, side, and filled quantity against the broker report. Compare the file or log timestamps in one time zone. Use the broker record for the actual execution price.
To isolate the difference, create a separately named strategy alert that only listens for order fills and sends a notification. Put the sample below in Message and keep the test disconnected from order routing. Compare a fresh Alerts Log entry with your strategy’s fill and recorded signal. If the log matches neither, check the saved script, inputs, symbol, interval, and fill settings. TradingView runs a saved copy of the strategy for each alert. Intrabar recalculation can also change what you see after a chart refresh.
Symbol {{exchange}}:{{ticker}}
Order {{strategy.order.id}}
Side {{strategy.order.action}}
Quantity {{strategy.order.contracts}}
Sim fill {{strategy.order.price}}
Fired (UTC) {{timenow}}Synthetic MES 5-minute candles. Times are bar closes in ET.
The 9:55 bar closes at 6,001.00. The market buy fills in the emulator at 6,002.25 on the opening tick of the bar ending at 10:00. A separate broker fill would come from an execution record.
In Alerts Manager, identify the alert’s exchange and dated contract. TradingView shows the exchange prefix there. Open that same symbol and check its chart status. TradingView uses a D marker for delayed symbols such as a delayed CME futures feed. Its CME Group coverage table lists a ten-minute free delay. Check the chart tied to your alert, since a different tab may display another expiry or feed.
Suppose a fictional price-crossing alert monitors a dated MNQ contract. The same crossing appears on a verified real-time feed at 10:20:05 a.m. ET. Your alert is on a symbol marked delayed. Alerts Log records the trigger at 10:30:06 and your phone shows it at 10:30:08. Most of the observed lag happened before the log entry, which is consistent with the ten-minute feed delay in this example. If the log records the trigger near 10:20 but the phone still displays it near 10:30, check notification delivery first.
Use the same clock and time zone for all three observations. This example uses a price crossing, so a rule that waits for a candle close would need its own comparison time. After checking exchange access, create a separately named, notification-only alert on the intended dated symbol and wait for a fresh event. Verify its log against the feed before relying on it. If you need a real-time reference, use a separately verified feed. CME notes that the public quotes on its website are delayed.
If you find no log event, open the saved alert and verify that it is active and has not expired. Inspect the exact dated futures symbol and data status. A chart for the new expiry does not update an alert created on the old contract. Compare the condition and crossing direction on the saved interval, using a completed bar when applicable.
If a trigger is logged and you expected a push notification, enable Notify on App for that alert and check the account logged into the mobile app. Confirm TradingView notification permission in iOS or Android settings. On Android, also check the device’s background or autorun controls if your phone provides them. TradingView suggests signing back in if the setup and permissions already match.
If the alert logged an event but no sound played, check Play sound and the browser tab or app volume. On Windows, check your browser volume in the system mixer. TradingView also documents browser-specific notification and autoplay controls. For a missing pop-up, check Show Pop-Up in the alert and the browser’s site notification permission.
Change one thing and wait for a fresh test alert. Record the Alerts Log time and the delivery time separately. Comparing the two helps you see whether the change fixed the trigger, the device delivery, or both.
Find the event by name and timestamp in the web Alerts Log. TradingView says the iOS app’s log shows events received as push notifications, so a missing row there can also mean delivery was suppressed. In Alerts Manager, hover over the calendar icon beside the alert status, if present, to see its saved days, hours, and time zone.
Suppose an MNQ crossing is logged at 8:55 a.m. Eastern and the alert is set to deliver from 9:30 a.m. to 4:00 p.m. Eastern on weekdays. The crossing can appear in the log while delivery is muted. A qualifying crossing at 9:35 a.m. on a weekday is inside that schedule. If the log shows the 9:35 event and your phone stays quiet, check the per-alert push option, the app login, and device permissions.
A muted event can leave an Only Once alert active, according to TradingView. Check the schedule on newly created alerts too, because a preset or your last-used settings can carry it over. To verify delivery, use a distinctly named alert with only push enabled and compare the next live trigger inside the saved window with the phone notification.
Find the alert in Alerts Manager and read the reason below its name before changing the trigger. Stopped after a trigger is expected for Only Once. An expired alert reached its configured end time. A manually stopped alert can be resumed after you confirm its saved symbol and condition. Check Alerts Log for the same alert name to see the events leading up to the stop.
TradingView limits regular alerts to 15 triggers in three minutes. In a fictional MES example, a recurring alert fires repeatedly as trades cross 6,010.00. Its log shows a burst of events between 10:00:05 and 10:02:30 a.m. ET. If TradingView reports that the alert fired too often, use that burst to identify what made it repeat before turning it back on. An earlier successful delivery and a later automatic stop can both be true.
Choose the trigger that matches your intent. If you need the first crossing, use Only Once on the price alert. If your rule requires a completed five-minute candle, use an interval-dependent condition and verify Once per bar close on that timeframe. If the alert uses Pine alert() calls, frequency is set in the script. After changing the script or its inputs, create a new alert so its saved copy uses those settings.
Verify the revised behavior with a separately named notification-only alert. Check the next qualifying live event, its Alerts Log timestamp, and whether the alert stays active for the next event when you intend it to repeat.
Find the expected event in Alerts Log. If there is no trigger row, check the saved symbol, condition and alert status first. If the row exists, check its Webhook status column and confirm that the alert had a webhook URL configured when it fired. The notification schedule also applies to webhooks. An event outside the saved window can be logged without a request reaching the destination.
Suppose the fictional MES alert above is logged at 9:55:07 a.m. ET, but its webhook status shows a timeout. TradingView gives the receiver three seconds to respond. Check the receiving app’s history at the same time. It may have recorded the request even though TradingView timed out waiting for a response. If the log instead shows an HTTP 4xx response, compare the saved destination and message format with the receiving app’s instructions. Record the exact status when contacting its support team.
Test changes with a separate notification-only destination. Give the test alert a distinct name and compare its trigger time and webhook status with the matching receipt in the receiving app. If your regular alert is connected to order routing, verify any orders, fills, and positions in the broker’s records before retrying. A webhook receipt alone cannot tell you whether an order was accepted or filled.
Open the saved alert and write down its exact exchange, root, month and year. Open that dated chart alongside the incoming contract, with the same bar interval and clock. If the old alert was based on Pine, check the saved script inputs and chart context too.
In this fictional example, both five-minute MES bars at 9:50 a.m. ET close below 6,010.00. At 9:55 the outgoing contract trades above that price and closes at 6,009.75. The incoming contract closes at 6,011.00. The saved bar-close crossing on the outgoing contract has no qualifying event. A missing log entry is consistent with those closes.
Set the intended level on the incoming dated chart before creating a replacement. Both charts use 6,010.00 here so you can isolate the expiry mismatch. In practice, a level derived from the old contract’s opening range or prior session may differ on the new one. Verify the replacement alert’s date code, timeframe and frequency, then retire the old alert if you no longer monitor that expiry. A new crossing alert waits for its own qualifying event.
If the saved symbol matches, compare the condition and both relevant closes before changing sound or push settings. If Alerts Log already shows a trigger, diagnose delivery separately. Verify orders through the broker’s record if you expected an order.
Synthetic MES and Incoming MES expiry 5-minute candles. Times are bar closes in ET.
Both dated contracts were below 6,010.00 at 9:50. At 9:55, only the incoming contract closes above. A saved close-based alert on the outgoing expiry has no qualifying crossing on the shown bars.
Open Alerts and check that the record shows the correct dated contract, condition, trigger, and expiration. For a technical alert, check its saved interval. Around rollover, confirm that the alert and the chart are still on the expiry you intend to monitor.
If a notification is missing, look in Alerts Log on the web first. If the trigger is there, check the delivery options and device notifications. If it is absent, check the alert status, data availability, direction, and whether the candle actually closed across the level.
After a notification, check the chart and follow your own order-entry plan. An alert in this walkthrough is a reminder to review the setup. Check the broker or paper account separately for any orders and fills.
Platform details on this page were checked against these official resources.
See how completed profiles and saved alert settings affect which levels can trigger.
Compare the original intrabar condition, the saved alert and the historical trade.
Compare Market Analyzer rearm settings and verify each trigger in Alerts Log.
Match the operating-system clock or UTC export with the chart bar.
Compare a crossing with a price that remains above a level while a filter catches up.
Compare a five-minute close with the last completed 15-minute candle.
Match the indicator window and compare three different closes against the range high.
Compare continuous and dated charts around the contract switch.
See how a wick differs from a close that confirms a breakout.
Verify the futures session before setting a line.
Verify the active account separately from the alert.
TradingView can wait for the next bar’s first trade to confirm the previous close. When no more trades arrive, such as at session end, TradingView says the server can confirm the final bar one minute after its scheduled close. Compare the Alerts Log and device notification time to see where the delay occurred.
Regular price alerts show Only Once and Every Time. For a bar-close setting, create an interval-dependent alert on a horizontal line or a suitable indicator.
Yes. A price crossing can occur while the candle is forming. If your condition depends on a completed candle, use an interval-dependent alert configured for Once per bar close.
Open the Alerts panel and review Alerts Log on the web. If it fired there, check your notification delivery. If it is absent, verify the saved condition, symbol, interval, and status.
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.