Alerts

Alerts are here to reduce screen-watching, not to outsource judgment.

Written By AxiomCharts

Last updated About 2 hours ago

Alerts

Alerts are here to reduce screen-watching, not to outsource judgment. That distinction matters with Axiom MA Pro because the indicator can watch several layers at once. Used well, alerts bring you back to the chart when a state changes. Used poorly, they turn a flexible context tool into a stream of commands you never fully verified. Use alerts when you already understand the state. Do not use them to skip understanding the state.

What alert families are available

Slot alerts

Each slot has three alert conditions:

  • MA XX Is Uptrend
  • MA XX Is Downtrend
  • MA XX Trend Change

Use these when one specific slot matters more than the whole stack.

Blend alerts

The blended line also has three alert conditions:

  • Blended MA Is Uptrend
  • Blended MA Is Downtrend
  • Blended MA Trend Change

Use these when you want a weighted summary state, not every slot detail.

Alignment alerts

The indicator also exposes:

  • All MA Slots Uptrend
  • All MA Slots Downtrend

Use these when full active-slot agreement matters to your workflow more than blended direction alone.

Two timing rules to keep separate

These are easy to blur together, so keep them distinct:

  • slot trust mode decides whether a slot reads confirmed higher-timeframe data or still-forming higher-timeframe data
  • alert timing decides when TradingView is allowed to fire the alert

In this script, every alert condition is gated by the chart bar closing. That reduces intrabar noise on the chart timeframe. It does not mean every slot inside the indicator is confirmed in the higher-timeframe sense. That leads to the rule most readers need stated plainly:

  • chart-bar-close alerts do not erase higher-timeframe repaint risk
  • if a slot has On Bar Close? turned off, that slot can still be reading a still-forming higher-timeframe bar when the alert fires

What has to be true before an alert can matter

An alert condition here is only meaningful when:

  • the relevant slot is enabled
  • the relevant slot has a valid value
  • the chart state already makes sense to you by eye

That matters for two common reasons:

  • slot alerts do not help if the slot is misconfigured or invalid on the current chart
  • alignment alerts consider active slots, not only the slots that shape the blend

A clean setup order

  1. Decide which chart state you actually care about.
  2. Verify that state visually on the chart first.
  3. Verify whether the relevant slot or slots are in confirmed mode.
  4. Verify whether those slots are actually shaping the blend, or only acting as local context.
  5. Create the alert only after the state makes sense without the alert.

If you reverse that order, you end up trusting the notification before you understand the condition.

When each alert type is usually useful

Alert typeGood useLess helpful use
MA XX Trend ChangeOne slot is your trigger layer and you want to know when it flipsYou have not decided why that slot matters more than the others
Blended MA Trend ChangeYou want a weighted regime shift rather than a single-slot flipYour blend is carrying too many loosely chosen weights
All MA Slots Uptrend/DowntrendYou want to review only when the active stack fully agreesYou are treating alignment as an automatic entry decision
MA XX Is Uptrend/DowntrendYou need persistent state for dashboards or downstream logicYou only wanted the moment of change, not the ongoing condition

Good fit for alerts, and poor fit

Alerts are a good fit when:

  • the state is rare enough that you do not want to monitor it constantly
  • you can explain the state in one sentence without looking at the alert name
  • you already know what you will check when the alert fires

Alerts are a poor fit when:

  • you are still experimenting with slot roles
  • the blend weights are still drifting around
  • you are using live-forming higher-timeframe mode but still reading it like confirmed history
  • you are hoping the alert will tell you whether the setup is good enough to trade

Hidden count plots

The script exposes hidden plots for:

  • Active Uptrend Count
  • Active Downtrend Count

These do not add visible chart clutter, but they can support alert workflows when you want the message or placeholder data to carry a little more stack context. Treat them as support utilities, not as the main proof surface.

Verification checklist before you rely on alerts

  • Confirm the relevant slot timeframes fit your chart timeframe.
  • Confirm the relevant slots are enabled.
  • Confirm whether the relevant slots are confirmed or live-forming.
  • Confirm whether a slot has zero blend weight and therefore does not shape the blend.
  • Confirm whether alignment and blend are actually the same condition in your workflow.
  • Confirm what you will verify on the chart after the alert fires.

A good first alert

If you are new to the indicator, start with one MA 03 Trend Change or one Blended MA Trend Change alert on a confirmed stack. That is usually easier to verify than enabling a full set of slot and alignment alerts at once. Once that behavior feels earned, expand deliberately.