> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quantnomad.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirmed vs Unconfirmed Signals

> Why TradingView indicator signals can appear and disappear on the current bar, what repainting is, and how to set up alerts that only fire on confirmed signals.

> [!NOTE]
>
> **General TradingView information.** This section describes standard TradingView behavior, not a QuantNomad-specific feature. TradingView updates its interface regularly, so menu names and positions may differ slightly from what you see. When in doubt, check the [TradingView Help Center](https://www.tradingview.com/support/).

If you've seen a signal appear on your chart and then vanish, or received an alert for a signal that isn't on the chart, you've seen the difference between an unconfirmed and a confirmed signal.

## How TradingView calculates the current bar

On historical bars, an indicator calculates once, using each bar's final open, high, low, and close.

On the **current bar** (the one still forming), the indicator recalculates on every price update. The "close" it uses is just the latest price, which keeps changing until the bar actually closes.

So a signal condition can be true at one moment and false the next:

```mermaid theme={null}
flowchart LR
  A[Bar opens] --> B[Price moves:<br/>condition true<br/>signal appears]
  B --> C[Price moves back:<br/>condition false<br/>signal disappears]
  C --> D[Bar closes:<br/>final result]
```

| | Unconfirmed signal | Confirmed signal |
| - | - | - |
| **Bar** | Current, still forming | Closed |
| **Can it change?** | Yes, until the bar closes | No |
| **Use for** | Early warning | Decisions and alerts |

## Repainting

**Repainting** is the broader term for an indicator showing different signals in real time than it shows on historical bars. The current-bar behavior above is the most common and expected form. Some indicators also repaint historical bars, for example when they use future data or certain higher-timeframe requests. That is a property of the specific indicator's code.

For indicator-specific behavior, see [How UT Bot v2 works](https://docs.quantnomad.com/free-indicators/ut-bot-v2/how-it-works.md#signal-timing) and [UT Bot Suite signals](https://docs.quantnomad.com/premium-indicators/ut-bot-suite/signals.md#signal-confirmation).

## Alerts that only fire on confirmed signals

Choose the trigger option when you create the alert:

| Trigger | When it fires | Confirmed? |
| - | - | - |
| **Only Once** | The first time the condition is true, then stops | No |
| **Once Per Bar** | The first time the condition is true during each bar | No |
| **Once Per Bar Close** | When the bar closes with the condition true | **Yes** |
| **Once Per Minute** | At most once per minute while the condition is true | No |

> [!TIP]
>
> Use **Once Per Bar Close** for signal alerts unless you specifically want early, unconfirmed warnings and understand that some will be false.

The trade-off is timing: a bar-close alert arrives at the end of the bar. On higher timeframes, that can be much later than the moment the signal first appeared.

## Related

* [Creating TradingView Alerts](https://docs.quantnomad.com/guides/tradingview-alerts.md)
* [Understanding Indicator Signals](https://docs.quantnomad.com/guides/indicator-signals.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.