Create and troubleshoot Phantom Flow Core alerts

Adding Core to a chart makes its alert conditions available. You still need to create a TradingView alert for the event you want to observe. A historical label does not automatically generate a notification.

Choose the event deliberately#

Core includes Phantom Shift Buy and Sell, Phantom Oscillator Buy and Sell, and Phantom Combo Buy and Sell. Combo requires the trend-flip and oscillator conditions together on the same bar. A green trend line on its own does not satisfy that condition.

Structure conditions distinguish internal events from swing events. Core also exposes Equal Highs, Equal Lows, Bullish FVG, Bearish FVG, and internal or swing OB Breakout conditions. An OB Breakout reports a zone break, not a touch. Read order block examples before selecting it.

Create one traceable alert#

1. Load the intended Core script on the exact symbol, exchange, and timeframe you want to observe.
2. Set its inputs and record them with a screenshot.
3. Open TradingView's Create Alert dialog and select Phantom Flow Core in Condition.
4. Select the exact named event, rather than a similarly named plot or another indicator instance.
5. If evaluating completed chart bars, choose Once Per Bar Close where available.
6. Set the notification destination and give the alert a name containing its symbol, interval, and event.

TradingView saves the script, inputs, symbol, and timeframe when an alert is created. Later chart edits do not update that running copy. Recreate the alert after changing the configuration you intend it to use. Alerts run on TradingView's servers and trigger on realtime events, not old historical labels. See TradingView's alert documentation.

If no notification arrives#

First inspect the alert log. If there is no event there, check whether the alert is active, whether the relevant market supplied a new bar, and whether its saved condition actually occurred. Compare the exact interval and exchange. A Combo alert can legitimately remain silent through many individual Shift or Oscillator events.

If the event appears in the log but not on your device, investigate notification settings and permissions. That is different from the indicator failing to detect a condition. Preserve the log timestamp before changing anything.

If an alert seems different from the chart#

Check whether you changed inputs or the script after creating it. Compare the alert's saved context with the current chart. Then compare its frequency with the time you took the screenshot. A condition seen during an open candle can differ from the final state.

Once Per Bar Close refers to the chart bar. It does not establish that a requested higher-timeframe candle is confirmed, or resolve the Core FVG timing caveat. Consult repainting and confirmation.

Use the alert diagnostic to choose your next check and prepare a support report. Keep the alert message, log timestamp, settings, and a chart screenshot when contacting support. An alert is an indicator notification, not an order, an execution record, or a complete trading system.