Alerts

Alerts

Axiom MA Osc Lite provides 18 alert conditions. All of them are bar-close gated at the chart-bar level — they only evaluate on confirmed (closed) chart bars, so intrabar price fluctuations on the chart bar will not trigger alerts.

This page covers every condition, the recommended TradingView trigger mode for each, and — just as importantly — the places where alert users commonly overtrust what the alert is telling them. An alert is a notification that a condition was true on a completed bar. It is not a recommendation, not a signal, and not a reason to act without checking the context. The gap between "the alert fired" and "I should do something" is where your own judgment lives.

How bar-close gating works

Every alert condition in this indicator checks barstate.isconfirmed before evaluating. This means:

• An alert will never fire while a bar is still building. It fires only after the bar closes and is finalized.

• This applies regardless of the On Bar Close setting. Even if On Bar Close is off and the oscillator is using live HTF data, the alert itself waits for bar close before checking the condition.

• The practical effect: when you receive an alert, the condition was true on a completed chart bar. If On Bar Close is off, the higher-timeframe input behind that alert can still come from a building HTF candle, so the later historical chart may not display the exact same intrablock reading that triggered it.

Alert types: continuous-state versus edge-triggered

The 18 conditions fall into two categories, and the distinction matters for how you configure them in TradingView.

Continuous-state alerts fire on every confirmed bar where the condition is true. If a slot is in bullish regime for twenty bars in a row, the "Is Bullish" alert is true on every one of those bars. With TradingView set to "Once Per Bar Close," this produces twenty alerts — one per bar.

Edge-triggered alerts fire only on the bar where the condition changes. A regime flip alert fires once — on the bar where the regime changed from bullish to bearish or vice versa. If the new regime persists for twenty bars, the alert does not fire again until the next flip.

This distinction is critical for managing alert noise. A continuous-state alert with "Once Per Bar Close" will fire repeatedly as long as the condition holds. If you want to be notified only when something changes, use edge-triggered conditions or switch the continuous-state alert to "Only Once" (though this means you will not be re-notified if the condition resets and then becomes true again later).

Per-slot regime alerts (9 conditions)

Three conditions per slot, applied identically to MA 01, MA 02, and MA 03.

Is Bullish (continuous-state)

Is Bearish (continuous-state)

Regime Flip (edge-triggered)

Overtrust risk with per-slot alerts: Treating a single slot's regime flip as an entry trigger. A regime flip tells you that the Fast line crossed its Slow line on one timeframe. It does not tell you about the other slots, the blended state, the broader trend, or anything about what happens next. A flip with a Slow Length of 3 is a small crossing that can reverse quickly. Context from the other slots and from the blended regime matters more than any single-slot transition.

Blended oscillator alerts (7 conditions)

These evaluate the blended (composite) oscillator — the weighted average of all enabled slots.

Blended Is Bullish (continuous-state)

Blended Is Bearish (continuous-state)

Blended Regime Flip (edge-triggered)

Crossed Above Zero (edge-triggered)

Crossed Below Zero (edge-triggered)

Overbought (edge-triggered)

Oversold (edge-triggered)

Overtrust risk with blended alerts: The blended regime flip and the zero-cross alerts are the most commonly overinterpreted. A blended regime flip feels significant — "the whole oscillator just changed direction" — but it may be a single heavy slot flipping while the others were already on that side. The zero cross feels decisive — "the oscillator just went positive" — but it is a mathematical crossing point in a weighted average, not a structural momentum reversal. Both alerts are useful as attention triggers. Neither is reliable as a standalone entry or exit signal.

Alignment alerts (2 conditions)

All Slots Bullish (continuous-state)

All Slots Bearish (continuous-state)

How disabled slots affect alignment: Disabled slots are excluded from the count. If two slots are enabled and both are bullish, "All Slots Bullish" fires even though the third slot is disabled. Alignment is evaluated only against the active slot population.

Overtrust risk with alignment alerts: Alignment is the alert most likely to be treated as "confirmation" — as if all timeframes agreeing means the trade is safe. It does not. Alignment is a backward-looking observation: all of the configured MAs at all configured timeframes have had price on the same side for some period. It is consistent with a strong trend in progress — and it is also consistent with the end of a trend where the slowest slot has finally caught up just as the move exhausts itself. Some of the worst entries happen right when alignment arrives, because the last holdout slot flipping often means the easy part of the move is over. The alert tells you what is happening now, not what happens next — and "all slots agree" is not the same as "this trade is safe."

Hidden count plots for alert message templates

The indicator includes two hidden plots that exist solely to support custom alert messages:

• Active Bullish Count — the number of enabled slots currently in bullish regime

• Active Bearish Count — the number of enabled slots currently in bearish regime

These plots are invisible in the pane (display.none) but can be referenced in TradingView alert message templates using:

{{plot("Active Bullish Count")}}{{plot("Active Bearish Count")}}

Example usage: You set up a "Blended MA Osc Regime Flip" alert with a custom message:

Axiom MA Osc Lite regime flip on {{ticker}} {{interval}}.Bullish slots: {{plot("Active Bullish Count")}} | Bearish slots: {{plot("Active Bearish Count")}}

When the alert fires, the message will include the count of how many slots are in each regime, giving you immediate context about whether the blended flip is backed by all slots or driven by a weight imbalance.

Alert summary table

Managing alert noise

Continuous-state alerts with "Once Per Bar Close" frequency will fire on every qualifying bar. During a sustained trend where all slots are bullish, the alignment alert alone fires once per bar — potentially hundreds of times over a trending session. That is not useful notification; it is spam that trains you to ignore alerts, which is worse than not having them.

Practical recommendations:

• Use edge-triggered conditions (Regime Flip, zero-cross, OB/OS) as your primary alert type if you want to be notified when something changes. These fire once on the transition bar and stay quiet until the next change.

• Use continuous-state conditions with "Only Once" trigger if you want to know when a state is first entered, without repeated notifications.

• Reserve continuous-state with "Once Per Bar Close" for automation or logging purposes, not for push notifications to your phone. If your phone vibrates every bar for an hour, you will turn the alerts off — and then miss the one that mattered.

• Combine the regime flip alert with the hidden count plot message template to get immediate context about the alignment state when the flip fires. This gives you "what changed" and "what the current agreement looks like" in one notification.