Alerts
This indicator provides alerts for per-slot regime states, blended regime events, cross-level events, and multi-timeframe alignment. Every alert fires only on confirmed (closed) bars. This page documents what each ale...
Written By Axiom Admin
Last updated About 1 month ago
Alerts
This indicator provides alerts for per-slot regime states, blended regime events, cross-level events, and multi-timeframe alignment. Every alert fires only on confirmed (closed) bars. This page documents what each alert detects, what it actually confirms, what it does not confirm, and where the common over-trust patterns are.
How alert gating works
All alerts in this indicator are bar-close gated. They check barstate.isconfirmed before firing, which means:
The alert evaluates only after the current chart-timeframe bar has closed.
No alert fires on intrabar price movement.
This prevents alerts triggered by brief spikes or wicks that reverse before the bar closes.
Bar-close gating is a deliberate safety choice. It means you will never get an alert on a wick that is already gone by the time you see the notification. The tradeoff is that every alert is delayed by the duration of one chart bar.
The On Bar Close interaction
There is a subtle but important distinction between the alert gating and the data freshness behind it.
Alert gating is about the chart timeframe. The alert fires after the chart bar closes.
Data freshness is about the slot's higher timeframe. If On Bar Close is ON (default), the slot values that the alert references are confirmed HTF values β stable and non-repainting. If On Bar Close is OFF, the slot values include unconfirmed HTF data that may change when the HTF bar closes.
In practice: when On Bar Close is OFF, an alert can fire on a confirmed chart bar, referencing slot values that are still provisional on the higher timeframe. The alert itself is honest β it tells you what the condition looked like at chart bar close β but the underlying data may shift after the alert fires if the HTF bar has not closed yet.
The safest configuration for alerts is On Bar Close = ON (the default). In that configuration, the alert fires on confirmed chart data referencing confirmed HTF data. Both layers agree.
Per-slot alerts
These alerts track individual slot regime states. They fire based on the slot's K (normalized MACD) and D (normalized Signal) values.
MACD 0X Is Bullish
What it confirms: That specific slot's normalized MACD line is currently above its normalized Signal line. Momentum at that timeframe favors the upside right now.
What it does not confirm: That this will persist on the next bar. That other slots agree. That price is also in a bullish structure. That the reading is fresh (it may have been bullish for many bars already).
This is a state alert, not a transition alert. It fires on every confirmed bar where the condition is true, not just the first bar where it becomes true. If you want to know when the regime changed, use the Regime Flip alert instead.
MACD 0X Is Bearish
Same logic as the bullish alert, inverted. The slot's normalized MACD is below its Signal. Momentum at that timeframe favors the downside.
MACD 0X Regime Flip
What it confirms: That the slot's regime just changed. A crossover happened between K and D on that slot.
What it does not confirm: That the new regime will persist. Brief flips near the crossover point are common, especially when K and D are close together. If K barely crossed above D and the histogram is thin, the flip may reverse on the next bar.
What to watch for after this alert fires:
How far apart are K and D after the cross? A narrow cross is less convincing than a wide one.
Is the histogram expanding in the new direction? That suggests the flip has momentum behind it.
What are the other slots doing? A regime flip on one slot while the others remain unchanged is a weak signal compared to multiple slots flipping in sequence.
Blended alerts
These alerts track the weighted consensus across all enabled slots.
Blended MACD Is Bullish
What it confirms: The weighted cross-timeframe consensus currently favors upside momentum.
What it does not confirm: That all individual slots agree. That the consensus is fresh. That any specific timeframe is bullish. The blend is a weighted average β it can be bullish even when some slots are bearish if the bullish slots carry more weight.
Blended MACD Is Bearish
Same as above, inverted.
Blended MACD Regime Flip
What it confirms: The weighted consensus just shifted from bullish to bearish or vice versa.
What it does not confirm: That the new consensus will hold. The same caution about narrow crosses applies here. Additionally, if the blend is dominated by one heavily weighted slot, a blended regime flip may just mean that dominant slot flipped β not that the multi-timeframe picture changed broadly.
Blended MACD Crossed Above Zero
What it confirms: The weighted consensus crossed from negative to positive territory. The blended normalized MACD went from below zero (net negative momentum) to above zero (net positive momentum).
What it does not confirm: That momentum is strong. A zero cross can happen at a reading of +2 β barely positive. It tells you the direction changed, not the magnitude.
Blended MACD Crossed Below Zero
Same logic, inverted.
Blended MACD Overbought
What it confirms: The weighted consensus has reached the upper attention threshold.
What it does not confirm: That a reversal is imminent. On trending instruments, extended readings above the overbought level can persist for many bars. This alert means the reading is stretched, not that it is about to snap back.
Blended MACD Oversold
Same as overbought, inverted. Extended oversold readings are common on downtrending instruments.
Blended MACD Histogram Crossed Above Zero
What it confirms: The blended histogram turned positive. In this indicator, that histogram is the weighted average of each slot's independently normalized MACD-minus-Signal value.
What it does not confirm: That blended K just crossed above blended D. Those events often travel together, but they are not mechanically equivalent because the histogram is not the literal blended K-minus-D gap. The size of the histogram after the cross is supporting context, not a guaranteed acceleration read.
Blended MACD Histogram Crossed Below Zero
Same logic, inverted. The blended histogram turned negative. That does not guarantee blended D just crossed above blended K, even though the two often move in the same neighborhood.
Alignment alerts
These are the most powerful β and most misused β alerts in the indicator. They fire when all enabled slots that are currently returning values agree on a regime direction.
All MACD Slots Bullish
What it confirms: All of the enabled slots that are currently returning values agree that momentum favors the upside. Each counted slot independently has its MACD above its Signal.
What it does not confirm:
Freshness. Slot 01 may have flipped bullish 100 bars ago while Slot 03 just flipped now. The alignment is technically true, but the freshness β and therefore the actionability β is very different from a situation where all three flipped within a few bars of each other. The alert does not distinguish stale alignment from fresh alignment.
Synchronization. The slots do not have to flip at the same time to trigger this alert. They just all have to be bullish at the same moment. The alert can fire because the last holdout slot finally caught up, not because something new and synchronized happened.
Participation. An enabled slot that is still returning
naduring warmup or bad-data conditions is ignored by the alignment count. So this alert is about the enabled slots that currently have values, not about every slot you may have toggled on in settings.Continuation. The alert tells you the current state. It says nothing about how long the alignment will hold or what happens next. All three slots being bullish right now does not mean they will all still be bullish on the next bar.
All MACD Slots Bearish
Same logic as All Slots Bullish, inverted. All counted slots currently agree on bearish momentum. Same caveats about freshness, synchronization, participation, and continuation apply.
What to check after an alignment alert fires
Alignment alerts are the ones most likely to be over-trusted. Here is a concrete verification checklist for when one fires:
Check when each slot flipped to this regime. Scroll back and find the last regime flip for each slot. Did they all flip recently, or has one been in this regime for a long time while the others caught up?
Check the histogram direction. Is the blended histogram pushing farther from zero or drifting back toward it? Use that as supporting context, not as a literal blended K/D distance check.
Check where each slot sits on the scale. Are all slots in the same general range (e.g., all between +30 and +60), or is one near saturation while the others are mild?
Check what price is doing. Momentum alignment without price structure confirmation is a reading, not a decision. Is price at a level that supports the direction the oscillator is suggesting?
Check your weight distribution. If one slot is heavily weighted, the blend may have been bullish for a while, and the alignment alert fired simply because the last low-weight slot finally joined. That is a weaker signal than three equally weighted slots all arriving at the same conclusion.
The purpose of this checklist is not to make alignment alerts useless β it is to make them useful. An alignment alert that passes all five checks is genuinely informative: fresh agreement across timeframes, a histogram that is not immediately rolling back over, comparable readings, price structure support, and balanced weights. That combination is worth paying attention to. The problem is acting on the alert before doing these checks, because the alert alone tells you less than it feels like it does.
Alert summary table
Common alert over-trust patterns
Using "All Slots Bullish" as a standalone entry trigger. The alignment tells you the current state but not the timing, the freshness, or the price context. Entering a trade because the oscillator says all timeframes agree is treating consensus as certainty. It is a useful data point, not a complete decision.
This over-trust pattern is especially dangerous because the alert feels comprehensive β "all slots agree" sounds like the strongest possible confirmation. But the alert cannot tell you that Slot 01 has been bullish for an hour while Slot 03 just flipped five seconds ago. It cannot tell you that price is at resistance and the move may already be priced in. It cannot tell you that the alignment formed gradually as the last holdout slot caught up, rather than as a synchronized shift. The word "all" in the alert name creates a sense of completeness that the alert itself does not actually deliver.
Ignoring the On Bar Close setting when using alerts. If On Bar Close is OFF, the data behind the alert can shift after the alert fires. You might receive a "Blended MACD Regime Flip" alert, react to it, and then see the regime flip reverse when the higher-timeframe bar closes and the provisional values update. The alert was not wrong β it reported what was true at that moment β but the moment it reported was provisional. If you rely on alerts for decision-making, keep On Bar Close ON so both the alert gating and the underlying data are confirmed.
Treating OB/OS alerts as reversal signals. The overbought or oversold alert means the reading is extended. On a trending instrument, that extension can last much longer than expected. Acting on the OB alert alone β especially shorting an instrument that just crossed above the overbought level β is fighting the trend based on a single oscillator reading. The OB alert fires at the same level whether the instrument is exhausted at the end of a move or accelerating into a breakout. Those are very different situations, and the alert cannot distinguish between them.