Alerts

Alerts

The indicator provides 31 alert conditions across four categories. This page explains each one, teaches the difference between state alerts and edge alerts, and names the places where alert-based decisions are most likely to go wrong.

All alerts evaluate only on confirmed chart bars, regardless of each slot's On Bar Close setting. Even if a slot is updating intrabar with unconfirmed higher-timeframe data, alerts will not trigger until the chart-timeframe bar closes. That reduces same-bar noise. It does not mean every alert is based on fully confirmed higher-timeframe data.

State alerts vs. edge alerts

This distinction matters more than any individual alert condition. If you do not understand it, the notification volume from this indicator will either overwhelm you or mislead you.

State alerts fire on every confirmed bar where the condition is true. A slot that stays bullish for 20 bars fires the bullish state alert 20 times. State alerts tell you "the condition still holds." They do not tell you "the condition just started." Use them when you want ongoing confirmation that a particular state persists.

Edge alerts fire once, at the moment a condition changes. A blended regime flip alert fires on the bar where K crosses D — not on subsequent bars where K remains above or below D. Edge alerts tell you "something just happened." Use them when you care about transitions, not persistence.

Choosing the wrong type leads to one of two problems:

• Setting up a state alert when you wanted a transition notification produces a flood of repeated alerts.

• Setting up an edge alert when you wanted ongoing monitoring gives you one notification and then silence, even while the condition persists.

Per-slot alerts (20 conditions)

Each of the ten slots provides two state alerts: one bullish, one bearish. These fire on every confirmed bar where the condition holds, for any enabled slot.

Alert message format: "MACD XX is bullish (Fast > Slow) on {{ticker}} {{interval}}" or "MACD XX is bearish (Fast < Slow) on {{ticker}} {{interval}}".

What per-slot alerts tell you

A per-slot bullish alert means that one specific slot's normalized MACD is above its normalized signal line on the most recently confirmed bar. It tells you the momentum regime for that slot's timeframe and ticker context.

What per-slot alerts do not tell you

• They do not tell you when the regime started. A slot that has been bullish for 100 bars fires the same alert as one that just flipped.

• They do not tell you anything about the blend. One slot being bullish says nothing about whether the other nine agree.

• They do not distinguish between a slot barely above its D line (K = D + 0.1) and a slot strongly above it (K = D + 40). The alert condition is binary: K > D or K < D.

Notification volume

If you enable per-slot state alerts on three active slots, you will receive alerts on virtually every confirmed bar — because each slot is almost always either bullish or bearish. This is by design for systems that poll state, but it will flood a phone notification setup.

If you only want to know about transitions, per-slot alerts are the wrong choice. Use the blended regime flip alert or set up a TradingView alert with the "Once Per Bar Close" frequency option combined with an additional condition to filter for the transition.

Blended alerts (7 conditions)

These operate on the blended K, D, and Histogram values — the weighted composite across all contributing slots.

State alerts (2)

Same state-alert behavior as per-slot alerts — fires on every qualifying bar, not just on transitions.

Edge alerts (5)

Understanding the edge alerts

Regime Flip fires at the moment the blended K crosses the blended D line. This is the weighted consensus changing direction. It fires once — then stays silent as long as the new regime holds, even for hundreds of bars. The next alert comes only when the regime flips again.

Crossed Above/Below Zero fires when the blended K line crosses the zero midpoint. This is a different event than a regime flip. The K line can cross zero while still in the same regime (if the D line is also near zero and they crossed zero together without K crossing D). In practice, zero crosses and regime flips often cluster together, but they are distinct conditions.

Overbought/Oversold fires when the blended K crosses the configured threshold level. This is a crossover event, not a state. Once K is above the OB level, the alert does not fire again. If K dips below OB and then crosses back above it, the alert fires again on the new cross.

Critical interaction with ATR Sensitivity: The OB/OS alerts are threshold-based. At high ATR Sensitivity (2.0+), the oscillator reaches the OB/OS levels frequently because it saturates faster. The alert fires every time K crosses the threshold, which can be multiple times per session. At low sensitivity (0.3–0.5), the oscillator may never reach the threshold, and the alert never fires. The usefulness of OB/OS alerts depends entirely on your sensitivity setting. If the alert fires constantly or never fires, recalibrate the OB/OS levels or adjust sensitivity before concluding the alert is broken.

Histogram alerts (2 conditions)

What histogram zero-crosses mean

The histogram is the blended composite of each slot's normalized MACD-minus-signal value. When it crosses zero, that composite has turned positive or negative.

This often clusters near blended regime flips because both are reacting to MACD-versus-signal pressure. But the histogram is not literally the same thing as blended K minus blended D, so the histogram zero-cross and the blended regime flip are not mathematically interchangeable. Sometimes they line up. Sometimes they do not.

The histogram alerts are useful when your alerting logic explicitly cares about that slot-level MACD-minus-signal composite. If you mainly care about the blended K/D regime changing, the Blended Regime Flip alert is the cleaner condition.

Alignment alerts (2 conditions)

What alignment alerts tell you

All enabled slots agree on the regime direction. Momentum favors the same side across every monitored timeframe and ticker.

What alignment alerts do not tell you

Alignment is not confirmation in the way most traders use that word. Three slots on 5m, 10m, and 15m can align easily because they are tracking nearly the same price action at slightly different lags. Alignment across genuinely different timeframes (5m, 1H, 4H) is rarer and more meaningful — but the alert cannot distinguish between the two. It just counts.

Disabled slots do not block alignment. If you have ten slots and only three are enabled, the alignment alert fires when those three agree — regardless of what the other seven would have shown.

An enabled slot with K exactly equal to D (neither bullish nor bearish) does block alignment. That is a rare edge case but it exists.

Alignment alerts are state alerts. They fire on every qualifying bar, not just when alignment first forms. If all slots stay aligned for 30 bars, the alert fires 30 times. There is no built-in alignment edge alert that only fires on the first qualifying bar.

Where alert users are most likely to overtrust

Overtrust 1: "Blended Regime Flip" as a trade entry signal

The regime flip tells you the weighted consensus just shifted. It does not tell you what shifted underneath.

Consider two scenarios that produce the exact same alert. In the first, all three slots have been contracting toward their signal lines for the last ten bars, and they all flip bearish within two bars of each other. The blend follows. The regime change is broad and gradual — the histogram was warning you for a while. In the second, two slots are solidly bullish, but a single heavily-weighted slot flips bearish and drags the blend with it. The blend flips even though the majority of timeframes still favor upside.

The alert fires identically in both cases. But the first scenario has multi-timeframe agreement behind it and the second is one dominant slot overriding two dissenters. Before acting on a regime flip alert, check the individual slot readings. The alert tells you the event happened. The slot lines tell you whether it means what you think it means.

Overtrust 2: "All MACD Slots Bullish" as a high-conviction buy signal

The alignment alert means every enabled slot is in the bullish regime. It does not mean:

• The readings are strong (some might be barely above their signal lines)

• The timeframes are genuinely distinct (all might be reading similar price action)

• The alignment is fresh (some slots may have been bullish for days while one just flipped)

• Price is going to go up (alignment is a momentum state, not a prediction)

Alignment is context. It narrows the search space. It is not a conclusion.

Overtrust 3: Assuming OB/OS alerts mean the same thing across sensitivity settings

At ATR Sensitivity 3.0, the blended K crosses the +70 OB level on most moderate up-moves. The alert fires frequently. At sensitivity 0.5, the oscillator rarely reaches +70 and the alert almost never fires. The same alert condition is dramatically more or less significant depending on a single setting.

If you change ATR Sensitivity, re-evaluate your OB/OS alert expectations. An OB cross at sensitivity 1.0 represents a genuinely extended reading. An OB cross at sensitivity 3.0 represents routine oscillator behavior.

Overtrust 4: Ignoring the state vs. edge distinction

A trader who sets up a per-slot state alert expecting a one-time notification will receive an alert every bar. A trader who sets up a regime flip edge alert expecting ongoing status updates will get one notification and then silence until the next flip. Neither alert is wrong — they are different tools for different jobs. The most common frustration with this indicator's alerts comes from choosing the wrong type, not from the alerts themselves.

Practical alert setup guidance

If you want to know when the consensus shifts

Use Blended MACD Regime Flip. It fires once on the flip bar and stays quiet until the next flip. When the alert comes in, open the chart and check the individual slot readings before acting. The alert is a prompt to look, not a prompt to trade. What you see in the slot lines — whether the flip is broad or driven by one dominant slot — determines how much weight the flip deserves.

If you want to know when all timeframes agree

Use All MACD Slots Bullish or All MACD Slots Bearish and expect repeated bar-close confirmation while the state persists. There is no built-in first-bar-only alignment alert, and the quality of the alignment still depends on how distinct your slot timeframes are.

If you want to know when the reading is extended

Use Blended MACD Overbought or Blended MACD Oversold. Make sure your ATR Sensitivity is calibrated so that these levels are reached meaningfully — not constantly and not never.

If you want ongoing regime status from one timeframe

Use the per-slot state alert for that slot. Accept the notification volume, or use TradingView's frequency options to limit it to "Once Per Bar Close."

If you want to minimize notification noise

Start with the edge alerts (Regime Flip, Zero Crosses, OB/OS Crosses). They fire only on transitions. Avoid per-slot state alerts unless you have a specific use case for per-bar confirmation. If you find yourself disabling alerts because of volume, the likely culprit is a state alert that should have been an edge alert — not the indicator being noisy. Review which alert type you chose before removing alerts entirely.