Alerts

Ten alert conditions ship with the Base trim. All ten evaluate on closed chart bars. None of them is an entry signal. Every one describes an ongoing state — "the relationship is currently like this on this closed bar" — not a transition event. If you want "just flipped" behavior, you build it externally.

This page is the contract for the alerts. What each one observes, what it gates on, what it does not attest to, and what to check after one fires. Read it before you route any alert into a chat channel, a strategy execution layer, or a mobile push. An alert that you do not understand is worse than no alert at all; it produces confident action on a condition you cannot describe.

The ten conditions, grouped

Six per-slot state alerts

Two per slot, one bullish and one bearish, for slots 01, 02, and 03.

• MA Osc 01 Is Bullish — fires when slot 01 is enabled and slot 01's fast sits above slot 01's slow on a closed bar.

• MA Osc 01 Is Bearish — fires when slot 01 is enabled and slot 01's fast sits below slot 01's slow on a closed bar.

• The same pair exists for slot 02 (MA Osc 02 Is Bullish, MA Osc 02 Is Bearish) and slot 03 (MA Osc 03 Is Bullish, MA Osc 03 Is Bearish).

A disabled slot does not fire its per-slot alerts. A slot with Blended Weight = 0 still fires its per-slot alerts as long as the slot is enabled — weight zero only removes the slot from the blend, not from the alert logic.

Two blend state alerts

• Blended MA Osc Is Bullish — fires when the blend fast sits above the blend slow on a closed bar.

• Blended MA Osc Is Bearish — fires when the blend fast sits below the blend slow on a closed bar.

If every enabled slot has Blended Weight = 0, or every enabled slot's fast value is na, the blend itself is undefined and these alerts do not fire. The pane also stops drawing the blend in that state.

Two alignment alerts

• All MA Osc Slots Bullish — fires when every enabled slot is on the bullish side of its own fast-vs-slow relationship on a closed bar.

• All MA Osc Slots Bearish — fires when every enabled slot is on the bearish side on a closed bar.

Alignment evaluates only against enabled slots. A disabled slot is not counted. Alignment does not care about weights; a weight-zero slot still participates in the alignment decision as long as it is enabled.

The bar-close gate

Every alert condition is gated by barstate.isconfirmed. That means the alert evaluates on the close of the chart bar it fires on, not on an intrabar tick. If the condition is true on the tick and becomes false before the bar closes, the alert does not fire. If the condition is false on the tick and true at the close, the alert fires when the bar confirms.

This gate is about alert evaluation, not about the slot's higher-timeframe value. If On Bar Close? is off and a slot is reading an evolving higher-timeframe bar, the alert fires on a confirmed chart bar using whatever the slot value was at that chart bar's close. The underlying higher-timeframe bar may still not be closed, in which case the slot value itself may move after the alert fires. See MTF & Repainting for the interaction.

What the alerts do not do

This is where the honest reading of the alerts lives. Every one of these is a common misread; if you are setting up an alert for something not named here, pause and reread Limitations & Trust Boundaries first.

• Alerts are not entry signals. None of them tell you to buy or sell. They describe a pane state. What you do with that state is a decision you make somewhere else, with rules you are accountable for.

• Alerts do not confirm direction of price. A slot can be bullish on a day price finished lower and bearish on a day price finished higher. Fast-vs-slow on the oscillator is about stretch-vs-its-own-smoothing, not about price direction.

• Alerts do not confirm independent evidence. The alignment alerts are the loudest case of this. All three slots agreeing says all three slots are on the same side of their own fast-vs-slow relationship — which, if the slots share source and overlap in timeframe structure, is close to one measurement repeated. Alignment looks like breadth. It is not breadth.

• Alerts do not describe transitions. Every alert is a state observation, not a flip notification. There is no "just crossed" condition in this script. If you want flip behavior, build it externally (TradingView's alert dialog supports "once per bar close" and transition triggers on custom conditions).

• Alerts do not trigger at the overbought or oversold lines. The script has no alert condition for crossing Overbought Level or Oversold Level. Those lines are reference zones; they drive how the pane is drawn, not when the pane yells.

• Alerts do not attest to intrabar price action. The alert fires based on the closed bar's state. Whatever happened inside the bar — including a stab deep into the reference band that was fully retraced before the close — is not visible to the alert.

After an alert fires: a verification routine

When an alert lands in your inbox or Discord or wherever you routed it, the useful questions are not "was the alert right?" They are "what exactly did the alert observe, and does that observation support what I want to do with it?" The alert is a state announcement. Whether it is useful is a separate question that the alert cannot answer by itself.

1. Find the bar. Open the chart at the alert's timestamp. The closed bar whose confirmation fired the alert is the bar where your cursor should land.

2. Check the configuration at the time. Were all three slots enabled? What were the weights? What was On Bar Close? set to? If anything has changed since, the alert was describing a different configuration than the one you are looking at now.

3. Read the blend and the slots on that bar. Confirm the alert's claim — e.g., that the blend was indeed bullish, or that every enabled slot was on the same side. The script is not lying about what it fired on; you are checking your own read of the pane.

4. Read the slow line's slope. A bullish blend with the slow line curling up toward the fast line is a different observation than a bullish blend with the slow pulling away downward. The alert conditions do not distinguish these; you do.

5. If On Bar Close? was off, check the higher-timeframe context. A slot value that was bullish at the chart bar's close may have been pulled from a higher-timeframe bar that had not yet closed. When the higher-timeframe bar eventually closes, the slot value may update. That update does not rescue or invalidate the alert — it is just a reminder that intrabar higher-timeframe reads are inherently fluid.

The alignment alerts deserve extra care

All MA Osc Slots Bullish and All MA Osc Slots Bearish are the two alerts in this pack most likely to mislead a serious trader. They sound like confirmation. They are a state observation across your configuration. If your configuration is three slots with the same source, similar baseline lengths, and stacked timeframes on an instrument where those timeframes move together, "all three bullish" is close to one measurement repeated three times. See the opening section of Limitations & Trust Boundaries — that page leads with this trap because it is the highest-damage misread in the Base pack.

A practical mitigation: before you route an alignment alert to a chat channel or to a strategy execution layer, ask whether the three slots are differentiated enough that their agreement is worth naming. If slot 01 is close on 5m EMA(20), slot 02 is close on 15m EMA(20), and slot 03 is close on 60m EMA(20), the three slots are doing nearly the same thing across near-overlapping windows. Differentiating source, length, or family on at least one slot changes the claim the alignment alert is making.

A second practical mitigation, for readers who want to keep alignment in their workflow without treating it as breadth: rename the alert in TradingView to something like "MA Osc: configuration agreement" when you set it up. It is a small move. It keeps you from accidentally treating "all three slots bullish" as "the market agrees," because the language on the alert itself no longer suggests that. The script cannot rename its own conditions; you can.

What is intentionally missing

These are gaps by design, not gaps you should expect a future update to fill at the Base level.

• No crossover / crossunder alerts. No "just flipped bullish" alert. If you want a transition event, layer it externally.

• No alerts on reference-line crosses. Overbought Level and Oversold Level are reference zones. They do not trigger.

• No alerts on midline crosses. Same reasoning.

• No cross-asset alerts. Base runs on the chart's symbol only; there is no second symbol to compare.

If a feature in this list is something you need, the CTX trim exposes a different alert surface and is worth reading before you commit to chaining things externally.

Where to go next

• Before you route the alignment alerts anywhere: Limitations & Trust Boundaries.

• If the alerts are firing at times that surprise you: MTF & Repainting and Troubleshooting.

• If you are trying to build a transition alert externally: see the Workflows page for the pattern, and then configure the TradingView alert with "Once per bar close" or a condition transition trigger outside this script.