Alerts

STR exposes a small, deliberate set of alert conditions. Each one reports a relationship that is true on a confirmed bar — nothing more. No alert calls a direction, none promises follow-through, and none fires during a developing bar. This page lists every alert, the literal trigger behind it, what the alert does and does not confirm, and the situations where an alert can quietly fail to fire, or fire on a narrower population than you intended, without anything being wrong.

An alert that is misread is more expensive than one that never fires. If you are wiring STR into any automated workflow or any decision-making rhythm where you will act on a notification without rechecking the chart, you want to have read this page end to end once. The rules are small; the failure modes from misreading them are not.

The confirmed-bar rule

Every single alert on STR is gated on a confirmed bar. That means the alert evaluates its condition after the current bar has closed, not during the live bar. Until that close, no alert will fire, regardless of what the chart looks like.

Consequences worth naming:

• You will never receive an alert from a flickering developing bar. If an indicator fires and then un-fires during a live bar, it is not STR doing it.

• Alerts arrive one bar after the state change. A cross that happened on bar N will be reported when bar N closes.

• A wick into and out of overbought during a bar does not create an alert. Only the closed state matters.

This is the honest default for any alert that reports on a chart's state. It is also the reason "no alert fired" sometimes means "the state was true at the mid-bar and then flipped back before close" — not "the indicator missed it."

Per-slot state alerts

Each of the five slots exposes a pair of alert conditions reporting whether the slot's fast oscillator is above or below its own slow line.

MA Osc 01 Is Bullish through MA Osc 05 Is Bullish

• Trigger. On the confirmed bar, this slot's fast oscillator is above this slot's slow line.

• What it confirms. The per-slot relationship was true at the moment the bar closed.

• What it does not confirm. That it will remain true on the next bar. That the blend is bullish. That any other slot is bullish. That the chart-price move is bullish.

• When it does not fire. If the slot is disabled (Enable MA nn is off). If the slot has not yet produced a current value because its higher-timeframe bar has not yet populated. If the slot's value is na for any reason.

MA Osc 01 Is Bearish through MA Osc 05 Is Bearish

• Trigger. On the confirmed bar, this slot's fast oscillator is below this slot's slow line.

• What it confirms and does not confirm. The same caveats as the bullish version, with the direction inverted.

• When it does not fire. Same as the bullish version.

Usage note: these alerts are per-slot reports, not per-timeframe reports. A slot configured to 5 minutes tells you about that slot at 5 minutes. Nothing stops you from configuring two slots to the same higher timeframe, in which case their alerts will usually (but not always) agree.

Blend state alerts

Two alerts report the state of the weighted blend between the blended fast and the blended slow.

Blended MA Osc Is Bullish

• Trigger. On the confirmed bar, the blended fast is above the blended slow.

• What it confirms. The aggregate relationship at bar close, weighted across the currently active slots with non-zero weights and valid current values.

• What it does not confirm. That every slot is bullish. That chart price is bullish. That the current level is low or high inside the pane. That the move has momentum in any directional sense beyond "fast is above slow."

• When it does not fire. If Plot Blend is off but the blend is still being calculated, the alert can still fire — Plot Blend only controls drawing. If every active slot has na on the current bar (for example during a warm-up window on a fresh chart), the blend itself is na and the alert cannot evaluate.

Blended MA Osc Is Bearish

• Trigger. On the confirmed bar, the blended fast is below the blended slow.

• What it confirms and does not confirm. Mirror of the bullish blend alert.

Usage note: when a single slot is carrying all the weight (weights collapsed to one slot), the "blended" alert is effectively a single-slot alert wearing the blend label. If you rely on the blend alert while your weights are collapsed, you are reading a single slot's state and calling it a blend.

Alignment alerts

Two alerts report whether every active slot with a current value is leaning the same way. These are the alerts most commonly misunderstood, so the caveat here matters.

All MA Osc Slots Bullish

• Trigger. On the confirmed bar, every active slot that has a current non-na value is bullish (its fast is above its slow).

• What it confirms. The set of active, currently-populated slots is unanimously bullish right now.

• What it does not confirm. That price will continue higher. That the oscillator level is high. That every slot you thought was active is contributing to the count. That a warming-up slot has been consulted.

• Silent-exclusion caveat. A slot that is enabled but has not yet produced a current value — for example, a higher-timeframe slot in the first minutes of a new chart load — is silently excluded from the alignment count. The alert can fire on a population of three slots even if you have five enabled, because two are still warming up. This is not a bug; it is the honest behavior. But it is worth naming, because a reader who believes "all five slots agree" is making a claim about two slots the indicator never consulted.

All MA Osc Slots Bearish

• Trigger and caveats. Same as the bullish version with the direction inverted.

Usage note: alignment is agreement at a moment in time. Agreement can occur at the start of a move, midway through, or near exhaustion. If you are going to act on alignment, the Workflows page covers the disciplines that make alignment useful rather than misleading.

Divergence alerts

Two alerts report confirmed divergence between the blended fast line and chart price. These are the alerts that most reward careful handling, because the markers on the pane and the alerts behind them have meaningful confirmation semantics.

Blended Bullish Divergence

• Trigger. On a confirmed bar that has confirmed a pivot low, chart price made a lower low while the blended fast made a higher low at the same pivot.

• Additional gate. The alert only fires when Show Div is enabled. If divergence is toggled off, the alert is silent even if the underlying condition is true.

• What it confirms. At the confirmed pivot, the oscillator disagreed with price about the significance of that low.

• What it does not confirm. That price will reverse. That the divergence will be the lowest low of the move. That another divergence will follow.

• When it does not fire. If Show Div is off. If the pivot has not yet confirmed (pivots require Pivot Len: bars on either side to close out). If Pivot Len: has been set so long that the chart has not yet accumulated a new pivot since the last one.

Blended Bearish Divergence

• Trigger and caveats. Mirror of the bullish version. At a confirmed pivot high, chart price made a higher high while the blended fast made a lower high.

A reader hooked on divergence alerts should remember: the alert will always arrive on the confirmation bar, even if you have Plot On Pivot? enabled to move the drawing backward visually. The visual position and the alert timing are not the same thing. The alert fires when the divergence becomes knowable, which is the confirmation bar.

What STR does not expose

There are alert conditions people sometimes expect to find on an oscillator like this. STR deliberately does not expose them.

• Overbought or oversold cross alerts. There is no alert that fires when the blended fast crosses above 70 or below 30. These levels are guides on the pane, not logic the oscillator acts on. If you want an alert on a specific level, build it yourself from the pane in your charting platform's price-alert system, but know that you are defining your own semantic — the indicator has not endorsed that level as a state change.

• BBWP compression-to-expansion alerts. BBWP is a percentile rank. STR does not expose an alert for the rank crossing in either direction. If you want that condition, you will be watching the columns by eye or building a paired indicator around it.

• Keltner band tag alerts. There is no alert that fires when the blended fast touches the upper or lower Keltner.

• Donchian break alerts. Same — no alert on the blended fast tagging the upper or lower Donchian line.

Naming these gaps explicitly is the honest posture. If any of them are the alerts you need most, STR on its own is not going to give them to you, and the right move is to build around it rather than to wait for it.

A practical note on setting up alerts

A few implementation details come up often and are worth naming together.

• "Once per bar close" is the correct alert frequency. Any other frequency is fighting the confirmed-bar gate STR already enforces.

• The alert will replay on each confirmed bar where the condition is still true. Blended MA Osc Is Bullish does not fire only on the cross; it fires any time the state is true at bar close. STR does not expose built-in cross-only alert conditions, so use these alerts as state reminders or build your own cross condition outside the script.

• Divergence alerts do not replay. A confirmed divergence fires once on its confirmation bar.

• If you change settings while an alert is armed, the alert will begin evaluating the new condition on the next bar. Nothing is retroactively reevaluated.

When an alert feels wrong

If an alert fired and you do not believe it, before you blame the indicator, walk three checks:

1. Is the condition actually true on the confirmed bar, not during the live bar? Scroll back one bar and re-read.

2. For alignment alerts, are all your enabled slots populated, or are some still warming up? The alignment count excludes na slots silently.

3. For divergence alerts, are you remembering the alert time or the plot time? With Plot On Pivot? on, the marker is drawn at the pivot bar but the alert fired at the confirmation bar.

If an alert did not fire and you expected one, walk three different checks:

1. Is the underlying extra enabled? Divergence alerts are gated on Show Div; a disabled extra will not fire.

2. Did the condition actually hold through bar close, or did it flicker mid-bar and revert?

3. Is the slot that you believed was bullish actually populated with a current value?

Most "wrong alert" impressions resolve inside those six checks. The alerts do exactly what this page says and nothing else. If that behavior does not fit what you want, the fix is to build the right alert in your charting platform's alert manager or a paired indicator around STR — not to tune an existing alert until it happens to agree with a different intent. Every time a reader tries the second move, the resulting workflow drifts further from what the alert actually confirms, and the gap between "what fired" and "what I thought fired" grows quietly until a surprising session exposes it.

A short word on alert hygiene

A final note that applies whether you use one alert or all of them. Alerts exist in a relationship with attention. Nine alert conditions firing on every confirmed bar where they are true is ambient noise, not information; a reader who cannot distinguish one firing from another has turned the alert system into decoration. Two disciplines help:

• Keep the minimum alert set that actually changes your behavior. If an alert fires and you do not open the chart to check, it is not earning its place. Disable it.

• Name what you expect to do when the alert fires. "Check the pane" is not a plan; "check whether BBWP has turned the corner yet" is. The named expectation is what makes the alert worth keeping.

These are not product features. They are the habit that makes the feature useful.