Alerts

Axiom CVD Osc CTX ships twenty-four alert conditions. Ten are per-slot bullish, ten are per-slot bearish, two are blended, and two cover stack-wide alignment. This page inventories all of them, names what each one actually commits to, and is explicit about what the alert surface does not include — because the alerts a reader expects and does not find are as important as the ones that are here.

The short version: every alert in this indicator is a state descriptor gated on a confirmed bar. None of them is a trade trigger. If you are wiring an alert to make a trade decision on its own, you are asking the pane to do a job it was not built for, and the pane will cheerfully do that job badly — the alerts will fire correctly, they will fire on every bar the state holds, and a downstream system that treats each fire as an event will over-trade until it either blows up or gets gated by its own operator. If you are wiring an alert as a "something worth attention just happened on the pane, come look," the alerts are well suited to that and the rest of this page covers how to set them up without the trade-trigger trap.

The distinction is not rhetorical. It shapes every choice documented below — especially around repeat-fire behavior, which is the single most surprising property of the alert surface for a reader coming from edge-triggered CVD tools.

The alert inventory

Per-slot bullish — ten alerts

Named CVD 01 Is Bullish through CVD 10 Is Bullish. Each fires when all three of the following are true:

• The slot is enabled (Enable CVD NN = true).

• The chart bar is confirmed (closed).

• The slot's CVD is above its signal when that chart bar closes. If On Bar Close? is OFF, the slot value can still be the live higher-timeframe value at that chart close and may change before the higher-timeframe bar closes.

Message body includes {{ticker}} and {{interval}} placeholders, so the TradingView alert will tell you which symbol and which chart timeframe fired it.

Per-slot bearish — ten alerts

Named CVD 01 Is Bearish through CVD 10 Is Bearish. Mirror of the bullish alerts: fires when the slot is enabled, the chart bar is confirmed, and the slot's CVD is below its signal at that chart close.

Blended alerts — two

• Blended CVD Is Bullish — fires when the bar is confirmed and the blended CVD is above the blended signal.

• Blended CVD Is Bearish — fires when the bar is confirmed and the blended CVD is below the blended signal.

The blended alerts respect whatever weight mixture you have configured. If all your weights are on slots 01 and 02, the blend is effectively a two-slot weighted mean and these alerts fire off that mean.

Alignment alerts — two

• All CVD Slots Bullish — fires when every enabled slot is bullish on a confirmed bar. Slots disabled entirely do not vote. Slots whose CVD value is na (for example, a slot waiting for intrabar history to arrive) do not vote. The alert fires when all the slots that can vote are voting bullish.

• All CVD Slots Bearish — mirror.

These are the most conservative alerts in the set. With the default three-slot stack, the alignment alert fires only when CVD 01, CVD 02, and CVD 03 all sit above their own signals at the close. Disagreement on any active slot will silence it.

The two things every alert in this pack commits to

1. Confirmed bars only. Every condition is barstate.isconfirmed and (state). Nothing fires on a partial bar. A slot's state can wobble during the formation of an intrabar on a lower-timeframe chart — in particular when On Bar Close? is OFF — but the alert does not react to those wobbles. The alert waits for the chart bar to close, evaluates the state at that close, and fires or does not fire. See MTF & Repainting for the timing model this leans on.

2. Repeat-firing while the state holds. The conditions above are not edge-detected. CVD 01 Is Bullish fires on every confirmed bar where CVD 01 is bullish, not only on the bar where it crossed from bearish to bullish. If CVD 01 is bullish for thirty consecutive bars, the alert fires thirty times. This is a deliberate choice — it matches how most readers use these alerts, as a triage signal they can mute or acknowledge — but it is the single most common surprise for a reader coming from edge-triggered alert tools.

Section below covers the closest TradingView alert-layer approximations if you need flip-like behavior.

What is not in the alert surface

It is faster to learn these by reading them once than by hunting for them in the Inputs dialog and concluding they are broken.

• No "crossed overbought/oversold" alert. The 80 and 20 guides do not feed any alert. They are cosmetic reference levels only. If you want a threshold alert, build it on top of a per-slot plot using TradingView's own alert-on-plot mechanism.

• No "blend crossed a threshold" alert. Same as above — the blend's color change is on the blend-vs-blended-signal crossing, not on the blend crossing a numeric level.

• No divergence alert. The pane does not inspect price action; it has nothing to compare CVD to for divergence detection.

• No "slot changed color" or "slot crossed signal" edge alerts. The state alerts are not edge-detected. See the repeat-fire section below if you want that behavior from your alert.

• No per-optional-ticker symbol-name alert. The alert message embeds {{ticker}} which is the chart's ticker. A slot configured to read QQQ will fire its per-slot bullish alert when QQQ's reading is bullish, but the TradingView alert will identify the chart symbol, not the slot's optional ticker. If this is ambiguous in your setup, use the alert name itself (CVD 05 Is Bullish) to identify the slot and keep a note of what symbol that slot is configured for.

• No alert on a runtime error. Runtime errors (slot TF below chart, lower TF equal to or above slot TF, window below slot TF) are visible on TradingView's own status row. They do not fire any alert inside this indicator.

If a reader is used to a CVD tool that bundles "alert when CVD crosses 80" and "alert on divergence" as defaults, the shorter list here is not an omission — it is a deliberate choice. This pane does not have a reliable enough story to tell about either of those events to commit a named alert to them.

How to read a per-slot alert when it fires

Suppose CVD 02 Is Bullish just fired. Here is the honest reading.

• CVD 02 is currently above its own signal at the close of the chart bar.

• That says nothing about what CVD 01 is doing, or what CVD 03 is doing, or where the blend is.

• It says nothing about where price closed. A slot can be bullish while price is falling; the slot is reading participation, not price.

• It will fire again on the next confirmed bar if the state still holds.

The useful next move after a per-slot alert fires is almost always to look at the pane and answer three quick questions: Are the other slots agreeing or disagreeing? Where is the blend? Is this slot sitting near 50 (a weak bullish read) or near 80 (a strong one)? The alert is the "come look" trigger. The pane is where the answer lives.

How to read the blended alerts

Blended CVD Is Bullish says: the weighted mean of the active slots is above the weighted mean's own smoothed signal, at the close of the current confirmed bar. It is a summary alert and is useful when the summary is what you want.

What the blended alerts do not tell you:

• They do not tell you the slots agree. A blend that is lime because one heavy-weighted slot is bullish while two others are bearish still fires Blended CVD Is Bullish. If agreement matters, use the alignment alert instead.

• They do not tell you the blend just flipped. Same repeat-fire rule as per-slot alerts — the alert fires on every confirmed bar where the blend is on the bullish side of its signal, not only on the flip.

The alignment alerts (All CVD Slots Bullish / All CVD Slots Bearish) are the tighter cousins — they fire only when every active slot is pointing the same way. If your workflow cares about agreement across the stack, they are usually more useful than the blended alerts.

Turning a state alert into something closer to a flip alert

If you want "fire once when CVD 02 goes bullish, then stay quiet until it flips bearish and back," the way to get it is not inside this indicator. TradingView itself offers two mechanisms that can help, but neither changes the indicator's condition into true edge detection:

• When creating the alert in TradingView, set the frequency dropdown to Once Per Bar Close. That matches the script's confirmed-chart-bar gate and keeps the alert aligned with the state the pane actually commits to. It does not turn repeat-fire across bars into flip-only.

• If you use an Only Once style alert, it fires the first time the condition is true and then disarms itself. That may be the first bar of a new flip, but it may also be a state that was already true when you armed it. You will need to re-arm it manually after it fires.

If neither of those fits, the structurally correct move is to consume the state externally — via webhook into your own alerting stack — and debounce there. The pane's job is to report state honestly at every confirmed bar; flip detection is a post-processing concern. The reason the pane does not bundle a "flip" alert is that "flip" means different things to different readers. To one reader a flip is a single-bar crossover. To another it is a crossover that holds for three bars. To a third it is a crossover confirmed by the blend moving in the same direction. An indicator that bakes in one of those definitions as the flip would quietly lie to everyone whose definition is different. The honest move is to expose the state, let each reader define "flip" outside the pane, and be explicit about that boundary here.

Verification — how to confirm an alert is doing what you think

Before you rely on an alert in a live workflow, run this three-step check against it.

1. Confirm the alert fires on the timeframe you expect

Wire the alert on a test chart on the same timeframe you plan to use it on. Watch the next few bar closes. The alert should fire exactly at bar close on your chart timeframe when the state is true, and should not fire mid-bar. If it fires mid-bar or at strange intervals, check TradingView's alert-frequency setting.

2. Confirm the alert matches pane state

When the alert fires, look at the pane on the bar that just closed. Is CVD 02's line actually above its signal at that bar? Is its color at full opacity? If the alert and the pane disagree, you have a stale alert, a test chart that is not the same as your live chart, or a rare rendering lag; do not trust the alert until the two stories line up.

3. Provoke the opposite state to confirm the alert stops firing

If CVD 02 Is Bullish is wired, wait until CVD 02 is bearish, or manually set settings to push it bearish (raise the signal length, change the MA type, etc.). The alert should fall silent on bars where the state is no longer true. If it keeps firing when the state is obviously false, the wiring is wrong.

None of these checks takes more than a few minutes. Running them once on each alert you intend to use is cheaper than discovering an alert wiring error after a bad trade.

Using the alerts as triage, not as triggers

A concrete, documented way to use this alert surface:

• Tier 1 (the "come look" tier) — subscribe to one or two per-slot alerts that cover the timeframe you care about. Treat a firing alert as a cue to open the chart, not as an instruction to do anything.

• Tier 2 (the "agreement tier") — subscribe to the alignment alert (All CVD Slots Bullish or All CVD Slots Bearish). When this one fires, you know the whole stack is pointing the same way on this bar close. Combined with a visual read, it is a meaningfully tighter condition than any single slot.

• Tier 3 (the "summary tier") — subscribe to the blended alert if you want a state readout that respects your weight configuration. This is the most "blunt" of the three tiers and repays the least look-at-the-pane work of the three, but for the same reason it is the most likely to mask stack disagreement.

Workflows documents this pattern end-to-end with a specific slot configuration.

A note on alerts across optional-ticker slots

If you are running cross-ticker studies — a slot on your chart symbol plus a slot pointed at a different ticker — the per-slot alerts respect the slot's configuration, not the chart symbol. CVD 05 Is Bullish on a slot reading QQQ will fire when QQQ's CVD is bullish at the close of a chart bar. The alert message will embed the chart's ticker, not QQQ. Name the alert descriptively at creation time (SPY chart, CVD 05 on QQQ, Bullish) if the ambiguity matters.

Session mode on an optional-ticker slot can lead to the slot's window reset landing at a different wall-clock time than the chart symbol's — SPY resets at the US cash open, BTCUSDT resets at UTC midnight. The alert fires on the chart's bar close regardless; you are just getting a read from a slot whose window is on a different calendar. Workflows covers the session-mismatch caveat in more detail.

Three alert traps worth naming

1. Assuming an alert is edge-triggered. It is not. CVD 01 Is Bullish will fire on every confirmed bar that CVD 01 is bullish. If you are counting alerts as "flip events," you are overcounting.

2. Wiring a single per-slot alert as a trade trigger. Every per-slot alert is a one-slot, one-timeframe state read. The whole point of the multi-slot pane is that one slot is not enough context to act on; reducing to one alert undoes that.

3. Forgetting that Hide Plot does not silence per-slot alerts. A hidden slot still computes state, still evaluates its alert condition, and will fire its alert. If you want to silence a slot's alerts, disable the slot or detach the alert in TradingView — do not just hide its plot.

Where to go next

• For what the slot states actually look like on the pane when these alerts fire, Visuals & Logic.

• For the timing model the confirmed-bar gate leans on, MTF & Repainting.

• For a documented alert-triage workflow, Workflows.

• For what to do when an alert fires but the pane state disagrees, Troubleshooting.