Alerts
Axiom CVD Osc Lite provides alerts for per-slot regime states, blended regime states, blended regime transitions, zero crossings, and overbought/oversold crossings. This page covers what each alert fires on, what it a...
Written By Axiom Admin
Last updated About 1 month ago
Alerts
Axiom CVD Osc Lite provides alerts for per-slot regime states, blended regime states, blended regime transitions, zero crossings, and overbought/oversold crossings. This page covers what each alert fires on, what it actually confirms, what it does not, and where alert-driven workflows tend to go wrong.
All alerts are bar-close gated. They fire only on confirmed (closed) bars, regardless of the On Bar Close setting. You will never receive an alert based on an incomplete bar.
Per-slot regime alerts
Each enabled slot has two alerts:
What these are: state alerts, not transition alerts
These alerts fire on every confirmed bar where the condition is true, not just when the state changes. If Slot 01 is bullish for twenty consecutive bars, the alert fires twenty times (once per bar close).
This matters for how you configure them in TradingView. If you set the alert frequency to "Once Per Bar Close," you will receive a notification every single bar the state holds β which can be very frequent during sustained regimes. If you only want to know when a regime starts, the per-slot alerts are the wrong tool. The blended regime flip alert (below) fires on transitions, but there is no per-slot transition alert.
What these do not confirm
A "CVD 01 Is Bullish" alert confirms that the CVD line is above the Signal line for that slot on that bar. It does not confirm that the estimated buying pressure is strong, that the reading is near the extremes, or that the other slots agree. A +2 CVD above a +1 Signal is technically bullish. It is also barely distinguishable from neutral. The alert fires the same regardless.
Blended regime alerts
The Regime Flip alert is the one most people actually want. It fires once when the blended regime switches between bullish and bearish β not continuously while the regime holds.
The blended state alerts have the same frequency behavior as the per-slot alerts: they fire every bar the condition is true, not just at onset. Use them if you want continuous confirmation of the blended state. Use the Regime Flip if you want notification of the change.
Blended crossing alerts
These are single-fire crossover alerts. They trigger once at the crossing, not continuously while above or below the level.
The OB and OS alert thresholds use the values set in the Overbought Level and Oversold Level settings (default +70 / -70). If you change those levels, the alert thresholds change with them.
Alignment alerts
These fire when all enabled slots agree on regime. If three slots are enabled, all three must be in the same regime. If only one slot is enabled, that slot's regime alone determines the alignment β which means the alignment alert becomes equivalent to that slot's individual regime alert. That may not be what you intended.
Like the per-slot and blended state alerts, these fire on every bar the condition holds, not just at onset. If all three slots stay bullish for fifty bars, you get fifty alerts.
Hidden-slot behavior
Alerts are gated by the Enable toggle, not by the Hide Plot toggle. A slot that is enabled but hidden will still fire its bullish and bearish alerts. It will also still count toward alignment alerts.
This means you can receive an alert saying "CVD 01 Is Bullish" from a slot whose line is not visible on your chart. This is not a bug β it is the expected behavior when a slot is hidden for visual clarity but left enabled for blend and alert purposes. But it is disorienting if you do not expect it.
If you do not want a slot firing alerts, disable it entirely.
What alerts do not tell you
Alerts confirm that a computed condition crossed a threshold or entered a state on a confirmed bar. They carry no additional context about:
Whether the reading is meaningful. An alert can fire immediately after a Session reset when the oscillator's readings are based on thin data and a narrow normalization range. The threshold was crossed, but the reading may be a cold-start artifact.
Whether the estimate is reliable. Alerts confirm the participation model's output, not the quality of the input data. On an illiquid symbol where the model fell back to single-bar estimation, the alert fires the same as it would on a liquid instrument with rich intrabar data.
Whether the slots agree. A blended bullish alert tells you the weighted composite is bullish. It does not tell you whether the underlying slots agree or whether one strongly bullish slot is dragging a conflicted blend above its signal. For that, you need the individual slot alerts or the alignment alerts.
What to do about it. This is a context tool, not a signal generator. An alert surfaces a condition. The decision about whether to act, how to act, and what to verify first remains yours.
Practical guidance for alert setup
If you want to know when multi-TF pressure aligns: Use the All CVD Slots Bullish/Bearish alignment alerts. Set the frequency to "Once Per Bar Close" and expect them to fire continuously during sustained agreement. Consider pairing with a manual check of individual slot positions to confirm the agreement is not just correlated adjacent timeframes.
If you want to know when the overall regime changes: Use the Blended CVD Regime Flip alert. It fires once at the transition and stays quiet until the next flip. This is the lowest-noise alert in the set and the one most traders actually want. It tells you "something shifted in the composite view" β you then go to the chart and investigate what shifted and whether it matters.
If you want to know when pressure reaches an extreme: Use the Blended CVD Overbought/Oversold alerts. Remember that these use the normalized range β an "overbought" reading is relative to the current window, not to an absolute volume threshold. Early in a session, the OB/OS thresholds can be reached on modest volume because the normalization range is thin. An alert that fires within the first several bars of a Session-mode window is more likely to reflect cold-start mechanics than genuine extreme pressure.
If you want to reduce noise from state alerts: Avoid per-slot and blended state alerts unless you specifically need continuous confirmation. For most workflows, the transition and crossover alerts carry the information you actually want to act on, with far less notification volume. A common mistake is setting up three per-slot bullish state alerts and one alignment alert β during a sustained trend, that produces four alerts per bar close, every bar, for as long as the trend holds. If your phone is buzzing every five minutes with the same message, the alerts are not helping you β they are training you to ignore them.
What to check after an alert fires
An alert tells you a condition crossed a threshold. It does not tell you what to do about it. Before acting on any alert from this tool, check at minimum:
Where are you in the session or window? If the alert fired in the first few bars after a Session reset, the reading may be a cold-start artifact. Check how much data the normalization range has to work with.
Do the individual slots agree? A blended regime flip can come from all slots shifting together or from one strongly directional slot dragging the blend across its signal while the others are flat. The first scenario carries more weight than the second.
What does the candle structure look like? The alert reflects the participation model's classification of the underlying bars. If the bars are clean and directional, the classification is likely solid. If the bars are mixed or wick-heavy, the model is working with ambiguous input and the alert's informational quality is lower.
Is the reading relative or absolute? An OB/OS crossing tells you the normalized reading crossed a threshold within the current window. It does not tell you how much volume produced that reading. Check the raw volume bars for magnitude context.