Alerts
Axiom MA Pro provides per-slot trend alerts, blended trend alerts, and global alignment alerts. All of them are gated to chart bar close — they fire only after the chart bar completes, never during intrabar updates.
Written By Axiom Admin
Last updated About 1 month ago
Alerts
Axiom MA Pro provides per-slot trend alerts, blended trend alerts, and global alignment alerts. All of them are gated to chart bar close — they fire only after the chart bar completes, never during intrabar updates.
This page covers what each alert condition does, how to set one up, what to verify after an alert fires, and where the subtle trust gaps live.
Alert architecture
Every alert condition in Axiom MA Pro checks barstate.isconfirmed before evaluating. This means:
Alerts fire only when a chart bar closes, not during the bar's formation.
On a 5-minute chart, alerts can fire at most once every 5 minutes.
On a 1-minute chart, once every minute.
This reduces intrabar noise but introduces a fixed delay: the alert always reports the state as of the last completed bar, not the current moment. If you need to know what is happening right now, you need to look at the chart.
Per-slot alert conditions
Each of the ten slots (plus the blend) has three alert conditions. They work identically across all slots.
[Slot] Is Uptrend
A continuous alert fires on every bar where the condition is true, not just when the condition first becomes true. If you use TradingView's "Once Per Bar Close" frequency, this alert fires repeatedly — once per bar — for the entire duration of the uptrend.
When this is useful: When you want to know on every bar whether a specific slot is still in uptrend. Often used in combination with other conditions outside this indicator.
When this is noisy: When the slot has been in uptrend for a long time. You will get a notification on every bar close for the entire duration. If you want notification only when the trend flips, use the Trend Change alert instead.
[Slot] Is Downtrend
Same behavior as Is Uptrend, but for the downtrend state. Fires on every confirmed bar where the slot is in downtrend.
[Slot] Trend Change
This fires once — at the moment the trend flips — then goes silent until the next flip. It does not keep firing every bar.
When this is useful: When you want to be notified at the moment a specific timeframe's MA changes direction. This is the alert most traders want for monitoring structural transitions.
What it does not tell you: Whether the flip will stick. A single bar can produce a trend change that reverses on the very next bar, especially on short trend lengths or fast timeframes. The alert reports that the flip happened, not that it will persist.
Blended MA alert conditions
Blended MA Is Uptrend
Fires every bar where the blended trend is uptrend. Same continuous behavior as the slot-level uptrend alerts.
Blended MA Is Downtrend
Blended MA Trend Change
This fires once per flip, just like the slot-level trend change. What makes the blend's flip less predictable is that it depends on the weighted vote — a slot that was not even close to flipping on its own can cause the blend to flip if its weight tips the balance. When you get a blend trend change alert, check which slot(s) drove it.
Global alignment alerts
All MA Slots Uptrend
Full bullish alignment. Fires every bar for as long as alignment holds.
This alert does not account for how long alignment has been sustained. Fresh alignment and aging alignment fire the same way. It also does not account for how many slots are enabled — three-slot alignment and ten-slot alignment both fire the same alert.
All MA Slots Downtrend
Full bearish alignment. Same behavior as All Uptrend, in reverse.
Alert message placeholders
The indicator publishes two hidden data series — Active Uptrend Count and Active Downtrend Count — that you can reference in TradingView alert message templates. These series are plotted with display.none, so they never appear on the chart, but they are available as dynamic values when you create an alert.
This lets you build messages like: "3 of 5 slots in uptrend" or "Downtrend count: 4."
To use them, insert the placeholder name into the alert message template in TradingView's Create Alert dialog. The placeholder syntax follows TradingView's standard for referencing indicator plots in alert messages.
Continuous vs. edge-triggered: choosing the right one
Most traders want the Trend Change alert for monitoring structural transitions. The continuous alerts are more useful as components in multi-condition setups or automation workflows where you need to know the state on every bar.
What to verify after an alert fires
An alert tells you that a condition was true when the chart bar closed. It does not tell you what is happening now. Here is what to check:
After a Trend Change alert
Confirm the flip on the chart. Look at the slot's trend color on the most recent bars. The alert tells you the state at bar close — by the time you look, a bar or two may have passed.
Check whether other slots have also flipped, or whether this is an isolated change on one timeframe. A single slot flipping while the rest hold is very different from three slots flipping together.
Consider the slot's trend length. A short trend length (1–2) produces more flips. The flip may reverse on the next bar, especially on fast timeframes. A longer trend length flip is more meaningful because the direction change had to persist over a wider window.
Weigh which slot flipped. If it is the fastest slot in your stack, it may be reacting to short-term noise — the kind of move that the slower timeframes will ignore. If it is the slowest slot, it means the most stable structural reference in your stack has changed its mind. That is a different kind of information. The fastest slot tells you what happened recently. The slowest slot tells you what the market's broader posture has become.
After an alignment alert
Confirm the count. Check the Data Window for the Active Uptrend Count or Active Downtrend Count. Make sure the number matches the number of enabled slots. If you have five slots and four are in uptrend, the "All Uptrend" alert should not have fired — investigate whether a slot was just disabled or if the state changed between the alert bar and the bar you are looking at.
Ask how the alignment formed. Did the last holdout slot finally flip (the slow timeframe catching up to what the fast ones already showed)? Or did all slots flip in quick succession (a sharp, broad move hitting every level at once)? The first case often means the move is already mature by the time alignment forms. The second case may indicate a genuine structural shift, but it also happens during panic moves that reverse.
Consider how fresh the alignment is. Alignment that just formed is ambiguous — it could be the start of a sustained move or the final agreement at the tail end of one. Alignment that has persisted for many bars may be stable, but it also means the conditions for a break have had time to build.
Do not treat alignment as a trade signal. It is a bias filter. Full alignment tells you the stack leans one way. It does not tell you that leaning that way right now is the right move. See Limitations and Trust Boundaries.
After a blend trend change
Check which slot(s) drove the flip. The blend's trend is a weighted vote, so the flip usually traces back to one or two slots whose trend state or weight tipped the balance.
If the flip seems to come from nowhere — no individual slot had a visible trend change — check whether a hidden slot flipped, a weight was changed, or a slot was enabled/disabled.
The subtle trust gap: alerts on unconfirmed slots
All alerts wait for the chart bar to close before firing. But the underlying data that determines the alert condition may come from an unconfirmed higher-timeframe candle.
Here is a concrete scenario. You are on a 5-minute chart. Slot 03 is set to the 1-hour timeframe with On Bar Close off. At 10:35 AM, the forming hourly candle's data produces an uptrend reading for Slot 03. The 5-minute chart bar at 10:35 closes, and the alert fires: "Slot 03 is uptrend."
At 10:50 AM, price pulls back. The still-forming hourly candle's data changes. Slot 03 now reads downtrend. But the alert already fired fifteen minutes ago reporting uptrend. The hourly candle does not close until 11:00 AM. The alert reported a state that was true at that moment but was not final.
The result: the alert is chart-bar-confirmed (it waited for the 5-minute bar to close) but not HTF-confirmed (the hourly candle's data was still building). If you acted on the alert, you acted on preliminary information.
This is not a bug. It is a consequence of mixing chart-bar alert gating with per-slot repaint control. If you need alerts you can trust to reflect confirmed multi-timeframe data, make sure every slot that matters to you has On Bar Close enabled.
For a deeper explanation of confirmed vs. unconfirmed data and mixed-confirmation states, see MTF and Repainting.
Alert setup checklist
Decide whether you want notification at the moment of change (edge-triggered) or on every bar while a condition holds (continuous).
Choose the correct alert condition from the list.
Set TradingView's alert frequency. "Once Per Bar Close" is the most common choice for continuous alerts.
Optionally include the Active Uptrend Count or Active Downtrend Count placeholders in the alert message for context.
If any slot involved in the alert has On Bar Close turned off, understand that the alert may reflect unconfirmed HTF data. Consider whether that matters for your use case.