Alerts
The indicator provides 39 alert conditions organized into three categories: per-slot alerts, blended alerts, and alignment alerts. This page documents what each alert fires on, what it actually confirms, what it does...
Written By Axiom Admin
Last updated About 1 month ago
Alerts
The indicator provides 39 alert conditions organized into three categories: per-slot alerts, blended alerts, and alignment alerts. This page documents what each alert fires on, what it actually confirms, what it does not confirm, and where alert users are most likely to overtrust the notification.
How alerts work in this indicator
Every alert in this indicator is bar-close gated. This means:
An alert fires only after a chart bar has closed and been confirmed.
No alert fires during a bar's formation, regardless of what the oscillator is doing in real time.
This is true even when a slot has On Bar Close disabled. The slot's visual output may update intrabar (see MTF & Repainting), but the alert condition is only evaluated once the chart bar is complete.
This is a deliberate chart-timeframe safety design. The indicator separates what you see from what gets checked mid-chart-bar. It does not mean every alert is built only from confirmed higher-timeframe data. If a slot runs with On Bar Close disabled, the alert can still evaluate that slot's unfinished HTF value at the moment the chart bar closes.
Per-slot alerts
Each enabled slot has three alert conditions. With ten slots, that is a potential 30 per-slot alerts. In practice, you will only set up alerts for the slots you have enabled and care about.
Bullish regime alert
Condition: The slot is enabled, the bar is confirmed, and the slot's Fast is above its Slow.
Alert name pattern: "MA Osc 01 Is Bullish," "MA Osc 02 Is Bullish," etc.
Firing behavior: Continuous. This alert fires on every confirmed bar where the condition is true, not just on the bar where the condition first became true. If a slot stays in bullish regime for 50 bars, this alert fires 50 times.
Why this matters: If you set up a bullish alert expecting one notification when the slot turns bullish, you will get a flood of notifications instead β one per bar for the entire duration of the bullish regime. On a 1-minute chart during a sustained bullish period, that is one notification per minute for as long as the condition holds. Your phone buzzes sixty times an hour. This is the most common alert-setup mistake with this indicator, and it usually leads people to disable alerts entirely rather than switching to the right alert type. If you want a single notification at the transition point, use the Regime Flip alert below.
Bearish regime alert
Condition: The slot is enabled, the bar is confirmed, and the slot's Fast is below its Slow.
Alert name pattern: "MA Osc 01 Is Bearish," "MA Osc 02 Is Bearish," etc.
Firing behavior: Continuous. Same logic as the bullish alert. Fires every bar the condition holds.
Regime flip alert
Condition: The slot is enabled, the bar is confirmed, and the slot's Fast/Slow relationship changed direction on this bar (Fast crossed above Slow, or Fast crossed below Slow).
Alert name pattern: "MA Osc 01 Regime Flip," "MA Osc 02 Regime Flip," etc.
Firing behavior: Event-based. This alert fires once β on the bar where the regime changed. It does not fire again until the regime changes again in the opposite direction.
This is the alert most people want when they think of a regime-shift notification. It tells you the moment a specific slot changed from bullish to bearish or vice versa, without repeating on subsequent bars.
Blended alerts
These alerts evaluate the blended composite β the weighted average of all enabled and weighted slots.
Blended bullish regime
Condition: Bar is confirmed, Blended Fast is above Blended Slow.
Alert name: "Blended MA Osc Is Bullish"
Firing behavior: Continuous. Fires every bar the composite is in bullish regime.
Blended bearish regime
Condition: Bar is confirmed, Blended Fast is below Blended Slow.
Alert name: "Blended MA Osc Is Bearish"
Firing behavior: Continuous.
Blended regime flip
Condition: Bar is confirmed, the Blended Fast/Slow relationship changed direction on this bar.
Alert name: "Blended MA Osc Regime Flip"
Firing behavior: Event-based. Fires once at the transition.
Blended zero-line crossover
Condition: Bar is confirmed, Blended Fast crossed from below zero to above zero.
Alert name: "Blended MA Osc Crossed Above Zero"
Firing behavior: Event-based.
Blended zero-line crossunder
Condition: Bar is confirmed, Blended Fast crossed from above zero to below zero.
Alert name: "Blended MA Osc Crossed Below Zero"
Firing behavior: Event-based.
Blended overbought cross
Condition: Bar is confirmed, Blended Fast crossed above the overbought level (default 70).
Alert name: "Blended MA Osc Overbought"
Firing behavior: Event-based.
Blended oversold cross
Condition: Bar is confirmed, Blended Fast crossed below the oversold level (default -70).
Alert name: "Blended MA Osc Oversold"
Firing behavior: Event-based.
Alignment alerts
These alerts check whether all enabled slots agree on regime direction. They are the broadest-scope alerts in the indicator.
All slots bullish
Condition: Bar is confirmed, at least one slot is enabled, and every enabled slot has Fast > Slow.
Alert name: "All MA Osc Slots Bullish"
Firing behavior: Continuous. Fires every bar the condition holds.
All slots bearish
Condition: Bar is confirmed, at least one slot is enabled, and every enabled slot has Fast < Slow.
Alert name: "All MA Osc Slots Bearish"
Firing behavior: Continuous.
The threshold is absolute: If you have ten enabled slots and nine are bullish but one is bearish, the "All Slots Bullish" alert does not fire. It requires unanimous agreement.
Edge case with one slot: If only one slot is enabled, the alignment alert fires whenever that slot is in the matching regime. The condition is trivially satisfied. This is technically correct but probably not what you intended if you are using alignment alerts to measure multi-slot consensus.
Hidden slots count: If a slot is enabled but has its plot hidden, it still participates in the alignment check. A hidden bearish slot will prevent the "All Slots Bullish" alert from firing.
Alert message format
All alert messages use this template:
[Alert description] on [chart ticker] [chart interval]For example: "MA Osc 01 Regime Flip on AAPL 5" or "Blended MA Osc Crossed Above Zero on BTCUSD 15".
Important: The ticker and interval in the message are the chart's symbol and timeframe, not the individual slot's. If you have a slot pulling data from QQQ on a 60-minute timeframe while your chart is on AAPL 5-minute, the alert message will say "AAPL 5" β not "QQQ 60."
This can be confusing for cross-ticker setups. If you are running alerts on slots with Optional Ticker overrides, keep in mind that the alert notification will reference the chart context, not the slot context. You will need to remember which alert corresponds to which slot and ticker configuration.
What an alert does NOT confirm
This section is as important as the alert descriptions above. Every alert tells you something specific about the oscillator's state at bar close. It does not tell you several things that are easy to assume:
It does not confirm that the condition will persist
A bullish regime alert fires because Fast was above Slow at bar close. It does not promise that Fast will still be above Slow on the next bar. The regime can flip immediately.
It does not confirm anything about price direction
The alert tells you about the oscillator's state β which is a derived measurement of distance from a baseline. Price can move in any direction regardless of the oscillator's state. A bullish oscillator regime with price falling means price is still above the baseline MA but moving toward it. It does not mean the oscillator is wrong β it means the oscillator and price are telling you different things, and both are accurate.
It does not confirm trade-worthiness
No alert in this indicator is a trade signal. The oscillator measures state. What you do with that state β whether it aligns with your other analysis, your risk management, your position sizing β is outside the indicator's scope. Treating an alert as a trade entry is the most common misuse pattern, and the danger is that it feels disciplined. You set a rule ("when I get the regime flip alert, I enter"). The rule looks systematic. But the rule is based on one input β the oscillator's state at bar close β and ignores everything else that determines whether the trade makes sense. A real process uses the alert as a prompt to evaluate, not as permission to act.
It does not guarantee confirmed higher-timeframe data
The alert fires at chart-bar close and evaluates the slot values at that moment. If a slot has On Bar Close disabled, the value it contributes at that check is the live state of the higher-timeframe bar, not a confirmed HTF close. The alert is still chart-bar-close gated, but the higher-timeframe input can remain unfinished.
This matters most for the blended alerts. If the blend includes live-mode slots, the blended value at chart-bar close is a mix of confirmed and unfinished HTF data. You will not know from the alert notification alone which portion of the blended reading was stable and which portion was still drafting. If this distinction matters for your process, either keep all contributing slots in confirmed mode or build the habit of checking which slots are live whenever a blended alert fires. Also be careful reading these alerts back on historical charts: the live-mode request path can present cleaner historical HTF values than what a trader actually saw while the higher-timeframe bar was still forming.
Continuous vs. event alerts: choosing the right one
Alert volume expectations
The continuous alerts (bullish, bearish, alignment) fire on every bar the condition is true. On a 1-minute chart during a sustained bullish regime, a per-slot bullish alert would fire every minute. On a 5-minute chart, every five minutes.
Before enabling continuous alerts, consider:
How long the condition typically holds on your configuration
How many notifications per hour or per day that translates to
Whether your alert notification channel can handle the volume without becoming noise
If you want to know about regime changes without continuous notification, the Regime Flip alerts are almost always the better choice.
Setting up alerts: practical steps
In TradingView, right-click the indicator in the chart pane or use the alert dialog.
Select the specific condition you want. Each of the 39 conditions appears as a separate option.
Choose your notification method (popup, email, webhook, etc.).
Set the alert to expire or remain active based on your needs.
Recommendation for first-time setup: Start with the Blended Regime Flip alert. It gives you one notification when the composite direction changes, without the volume of continuous alerts or the granularity of per-slot alerts. Once you understand how often it fires and whether the composite regime flips are meaningful for your setup, add per-slot alerts for the timeframes or tickers that matter most.
Verifying alert behavior
After setting up an alert, confirm it is working as expected:
Check that it fires at bar close, not during the bar. Watch the chart near a condition threshold. The alert should fire after the bar completes, not while it is forming.
For regime flip alerts: Confirm the alert fires only when the color changes on the slot or blend, not on subsequent bars.
For continuous alerts: Confirm the alert fires repeatedly on consecutive bars while the condition holds.
For alignment alerts: Confirm the alert fires only when all enabled slots agree. Flip one slot out of alignment and confirm the alert stops.
Check the alert message: Verify that the ticker and interval in the message match your chart context. If you are running cross-ticker slots, remember the message references the chart, not the slot.