Why did my TradingView alert not fire?

A missing notification can mean that an alert never triggered, or that a recorded trigger did not reach the device you expected. Start with the TradingView alert log to separate those cases. The optional guided diagnostic asks only the questions needed for your next check and produces a support report. It cannot verify your account or chart. The same steps are available below without JavaScript.

If the event is in the alert log#

Preserve the event timestamp. Check the notification destination selected for that alert, then inspect the relevant app or browser notification settings. A log entry establishes that TradingView recorded a trigger; it does not establish delivery to a particular device. The diagnostic does not request or change notification permissions.

If the event arrived but seems different from the chart, compare the saved alert configuration with your current chart and note when the screenshot was taken.

If the event is absent from the log#

Check whether the alert was active when you expected the event. Note a pause, expiry, or error message before changing anything. Then compare the exact indicator instance, condition name, symbol including exchange, and timeframe. A historical label is not an event that will be sent retroactively.

TradingView saves a copy of the script, inputs, symbol, and timeframe at alert creation. A later chart change does not update that running copy. If you want the alert to use your revised configuration, record the old settings and recreate it from the intended chart. These platform behaviors are documented in TradingView's alert reference.

Check what the Core event actually means#

• Phantom Shift Buy or Sell marks a direction flip. An ongoing trend is not a new flip on every candle.
• Phantom Oscillator signals are thresholded momentum turns. Candle color alone does not establish an oscillator event.
• Phantom Combo requires the Shift flip and the Oscillator signal in the same direction on the same bar. Turning off the oscillator's Show Signals input prevents its contribution to Combo. Hiding Confluence Stars only hides the drawing.
• Core OB Breakout means a zone boundary broke according to its mitigation source. It is not an alert for a first touch or a newly drawn zone.
• Internal and swing structure are distinct. Match BOS or CHoCH and the structure scale to the selected condition.

Use Core alert setup to identify the available conditions. These names do not describe the Pro alert catalog. If the chart title says Pro, use the guide for that installed version. Core owners install their emailed script and do not need a Pro dashboard login or invitation.

Compare candle timing#

A condition observed while a candle is open can differ at its close. Compare the alert frequency with your observation time. Once Per Bar Close, where available, refers to the chart candle. It does not confirm a higher-timeframe candle.

Core higher-timeframe FVG history also has a lookahead caveat. A historical gap box alone cannot prove when it was available live. Record first appearance, the requested candle close, and the state after reload. Read repainting and confirmation before treating a historical drawing as evidence of a missed realtime alert.

Prepare a useful support report#

Record the edition and exact indicator version, condition name, symbol and exchange, timeframe, expected event timestamp with timezone, and whether the event is in the log. Include the saved settings and a redacted screenshot. If the script or inputs changed after alert creation, say so.

The diagnostic's copyable report includes selected answers only. Add chart details yourself when you contact support. Do not include passwords, payment details, the paid script, or your personal script access link. A completed checklist narrows the investigation; it does not prove a software fault or guarantee future notification delivery.