Alerts

Alerts

Axiom CVD Osc Pro provides 29 alerts: 20 per-slot alerts, 7 blended alerts, and 2 alignment alerts. All of them fire only on confirmed bars, regardless of the per-slot On Bar Close setting. This page catalogs every alert, explains what it does and does not confirm, and teaches you how to manage the noise.

How all alerts work in this indicator

Every alert condition is gated by bar-close confirmation. The indicator checks barstate.isconfirmed before evaluating any alert — so alerts fire only after the chart-timeframe bar has closed and its values are final. This applies to all 29 alerts uniformly.

What this means in practice: If you are watching a slot with On Bar Close turned off and the intrabar reading flips to bullish, the alert will not fire until the current chart bar closes. The alert lags behind what you see on the live chart. This is intentional — the alert reports the confirmed state, not the building state.

Per-slot alerts

Each of the 10 slots has two alerts: one bullish, one bearish. 20 alerts total.

These are state alerts, not edge alerts. They fire on every confirmed bar where the condition is true — not just when the regime changes. A slot that is in bullish regime for 50 bars will fire the bullish alert 50 times.

Why this matters: If you set up a per-slot bullish alert expecting it to notify you once when the regime flips, you will get a notification every bar for the duration of the regime. On a 1-minute chart, a 30-minute bullish run produces 30 alerts. Most users will want to pair these with TradingView's "Once Per Bar Close" frequency setting, or use the blended regime-flip alert (below) if they only want edge notifications.

What per-slot alerts do not confirm:

• They do not confirm that price moved in the direction of the delta bias.

• They do not confirm that the reading is strong or meaningful — a CVD of +0.5 above its Signal still triggers the bullish alert.

• They do not confirm cross-timeframe agreement. Each slot alerts independently.

Blended alerts

Seven alerts based on the blended CVD and Signal composite.

If every enabled slot has a blend weight of 0, or no positive-weight slot currently has a valid reading, the blended CVD/Signal stay na and the blended alert family has nothing to trigger from until a contributing slot comes online.

State alerts (fire every bar the condition holds)

Same behavior as per-slot state alerts. These fire every bar the blended regime condition is true.

Edge alerts (fire once at the crossing)

Edge alerts fire once — at the bar where the condition first becomes true. They do not fire again as long as the blended line stays beyond the threshold. A blended line that crosses above +70 and stays there for 40 bars produces one OB alert, not 40.

Regime Flip is the most useful blended alert for most traders. It fires when the blended CVD crosses its blended Signal in either direction. If you want a single notification that the aggregate directional lean has changed, this is it.

What blended alerts do not confirm:

• They do not confirm that the individual slots agree. The blended line can flip regime because one heavily weighted slot flipped, even if others disagree.

• The OB/OS alerts do not predict reversals. A cross above +70 means the composite is extended. In a trend, it stays extended.

• Zero-cross alerts do not confirm trend direction. They confirm that the weighted average of estimated pressure changed sign — which can happen from a genuine directional shift or from a dominant slot's session reset pulling the blend back to zero.

Alignment alerts

Two alerts that require unanimous agreement across enabled slots that currently have valid CVD readings.

These are state alerts. They fire every bar where the condition holds.

Blend weight does not matter here. A weight-zero observer slot still counts toward alignment as long as it is enabled and currently producing a valid CVD reading.

The bar is very high. With three enabled slots producing valid readings, all three must agree. With five or more, every valid-reading slot must be in the same regime. If one slot is barely in bearish territory (CVD is 0.1 below its Signal), alignment breaks. These alerts are strict by design — they report true multi-timeframe agreement across the slots that are actually contributing state on that bar, not approximate alignment.

What more slots means for alignment frequency: With three enabled slots producing valid readings, alignment breaks whenever one disagrees. With five or more, the probability of all valid-reading slots simultaneously agreeing drops significantly — especially if the slots span a wide timeframe range. A 5m slot responds to bar-to-bar noise, and one bearish bar can flip it out of bullish regime even while all the higher-TF slots hold. The wider the timeframe spread and the more slots you enable, the rarer alignment becomes and the more likely it fires only during sustained, decisive moves. That can be useful — or it can mean the alert fires so infrequently that it arrives after the move is already mature.

What alignment alerts do not confirm:

• They do not confirm the direction of the CVD lines, only the regime label. All slots can be "bullish" while their CVD values are declining — the regime has not flipped yet, but the momentum is fading. Alignment at that stage is a lagging read on a move that is losing steam.

• They do not weight by importance. A 5m slot in barely-bullish regime and a 1h slot in strongly-bullish regime both count equally for the alignment condition.

• NA outputs are excluded from the active-slot count rather than counted as disagreement. Alignment can still fire if the remaining enabled slots with valid readings agree, but it will not fire at all if no enabled slot is producing a valid CVD reading.

Managing alert noise

State alerts will be noisy by default

The per-slot and blended state alerts fire every confirmed bar where the condition is true. On low timeframe charts, this produces a high volume of alerts during sustained regimes. Options:

• Use TradingView's "Once Per Bar Close" alert frequency and pair it with the chart timeframe that matches your attention cadence.

• Use the Blended CVD Regime Flip alert instead if you only want to know when the aggregate direction changes.

• Use the All CVD Slots Bullish/Bearish alert if you only want to know when every enabled slot with a valid reading agrees — this fires less frequently because the bar for unanimous agreement is high.

Edge alerts will occasionally fire on noise

A blended zero-cross or OB/OS cross can be triggered by a single bar's values in low-volatility conditions. If the blended line is hovering near zero or near +70, it may cross the threshold, fire the alert, and then cross back the next bar. This is not a false alert — the condition was met — but it is a thin-data signal. When the blended line is near a threshold, individual crossings carry less information than when the line drives through the level with momentum from multiple bars.

What to verify after an alert fires

An alert tells you a condition was met. It does not tell you why, or whether the condition is still true by the time you see the notification. When you receive an alert:

1. Check the current state. Is the condition still holding, or did it reverse on the next bar?

2. Check the individual slots. If it is a blended alert, which slots are driving it? Is it broad agreement or one dominant slot?

3. Check the window context. Did a session just reset? If so, the alert may have fired on thin post-reset data.

4. Check price. The alert reports estimated volume delta condition, not price condition. Does the price action support the direction the alert is suggesting?

Alerts are starting points for attention, not endpoints for decision. The oscillator tells you what estimated pressure is doing. What you do with that information requires your own price context, risk parameters, and judgment.

A practical alert setup

If you are configuring alerts for the first time and want a low-noise starting point, consider this combination:

• Blended CVD Regime Flip — fires once when the weighted composite switches direction. This is the single most useful alert for most traders. It tells you the aggregate lean has changed without firing every bar.

• All CVD Slots Bullish / All CVD Slots Bearish — fires when every enabled slot with a valid reading agrees. Pair this with TradingView's "Once Per Bar Close" to avoid repeated notifications during sustained alignment. Treat it as a contextual heads-up, not a trigger.

What to leave off initially: per-slot state alerts. They fire every bar the condition holds, which on a low-timeframe chart produces dozens of notifications during a sustained regime. Add them only when you have a specific reason to monitor a single slot's regime and you have set TradingView's frequency control to manage the volume.

Start with two or three alerts. If you find yourself ignoring most of them after a week, you have too many — reduce to the ones that actually change what you look at on the chart.