Troubleshooting

Troubleshooting

This page is organized by what you see. Find the symptom, check the likely cause, and follow the fix. It also includes a section for behaviors that are not bugs — expected things that commonly confuse new users.

Problems with error messages

Red error banner: "MA 0x timeframe cannot be lower than the chart timeframe"

What you see: The indicator stops rendering. A red error banner appears at the top or bottom of the chart, identifying which slot has the problem (MA 01, MA 02, or MA 03).

Cause: The identified slot's timeframe is set lower than the chart's timeframe. A 5-minute slot on a 15-minute chart, or a 60-minute slot on a daily chart, triggers this.

Fix: Either raise the slot's timeframe in settings so it is at least as high as the chart timeframe, or lower the chart timeframe to match the slot. The rule is simple: every enabled slot's timeframe must be >= the chart timeframe.

Common scenario: You loaded the indicator on a daily chart without changing the defaults. The default timeframes are 5m, 15m, and 60m — all below daily. Change the enabled slots to daily or higher (weekly, monthly) to use the indicator on a daily chart.

Problems with lines not showing

MA line is missing or flat on recent bars

What you see: One or more slot lines do not render on the most recent bars, or they show as a flat line at what appears to be an old value.

Likely causes:

1. On Bar Close is on and the HTF bar has not closed yet (expected behavior). With On Bar Close on, the most recent value updates only when the HTF bar confirms. If the 60-minute slot has not yet received a new 60-minute close, it will show the last confirmed value. Wait for the next HTF bar close. See Not a bug: Lines "step".

1. The slot is disabled. Check settings and confirm the slot's Enable checkbox is on.

1. The slot's plot is hidden. Check whether "Hide Plot" is on for that slot. A hidden slot still computes and feeds the blend — you just cannot see it.

1. The Optional Ticker is set to an invalid symbol. If the alternate ticker does not exist or TradingView cannot resolve it, the slot may return no data. Check the Optional Ticker field in settings and verify the symbol is valid.

All lines disappeared

What you see: The indicator title appears in the chart's indicator list, but no lines are visible.

Likely causes:

1. All three slots are disabled. Check that at least one slot's Enable checkbox is on.

1. All slots and the blend have their plots hidden. Hiding is not disabling — the indicator is still computing, but nothing is drawn on the chart. Check Hide Plot for all four elements (MA 01, MA 02, MA 03, Blended MA).

1. A runtime error is present but not immediately visible. Look for a red error banner. On some chart layouts, the banner can be partially hidden behind other elements.

Problems with the blended line

Blended line does not sit between the visible slot lines

What you see: The blended MA line appears above, below, or offset from the visible individual MA lines, rather than "between" them as expected.

Likely causes:

1. A hidden slot is pulling the blend. If a slot has its plot hidden but is still enabled with a non-zero weight, its value feeds the blended calculation. The blend reflects all enabled slots, not just the visible ones. A hidden slot in a significantly different position (especially one using an alternate ticker) can pull the blended value away from the visible lines.

1. Weights are very unequal. If one slot has 80% weight, the blend tracks almost entirely with that slot. If that slot happens to be above or below the others, the blend will sit near it, not between all three.

Fix: To identify the cause, temporarily unhide all slots and equalize the weights (33.3 each). If the blend now sits between the three, the issue was hidden slots or unequal weights. Adjust from there.

Blended line color does not match the majority of slot colors

What you see: Two out of three slots show solid color (uptrend) but the blended line is red, or vice versa.

Cause: The blended trend is a weighted vote, not a majority vote. If the single dissenting slot carries more weight than the two agreeing slots combined, the blend follows the heavier side. For example, if the dissenting slot has 50% weight and the two agreeing slots have 25% each, the blend follows the 50% side.

Fix: This is working as designed. If you want the blend to follow the majority of slots, equalize the weights so no single slot can override the other two. See Visuals & Logic and For the Geeks for the full explanation.

Problems with cross-ticker mode

Cross-ticker MA line drifts away from chart price

What you see: A slot using an alternate ticker gradually separates from the chart's price action. The line was near price initially but has moved to a noticeably higher or lower level over time.

Cause: The chart symbol and the alternate ticker have diverged. The scaling ratio (chart close / alternate close) stretches when the two assets move apart. If AAPL drops while SPY rises, the ratio decreases and the scaled MA falls relative to where it would otherwise be. This drift is ratio movement, not trend information.

Fix: This is expected when assets diverge. You can:

• Accept the drift as information — it tells you the relationship between the two assets has weakened

• Switch to a different alternate ticker that is currently more correlated with the chart symbol

• Disable the cross-ticker slot if the divergence makes the scaled line uninformative

See Limitations & Trust Boundaries and For the Geeks for deeper explanation.

Problems with alerts

Alert not firing

What you see: You created an alert but it does not fire when you expect it to.

Likely causes:

1. The slot is disabled. All alert conditions require the relevant slot to be enabled. A disabled slot produces no alerts.

1. The MA value is na. If the slot has no valid data (e.g., an invalid alternate ticker, or the very beginning of the chart where there is not enough history to compute the MA), the alert condition will not be true.

1. TradingView alert frequency mismatch. If you used a one-shot bar-close notification mode with a continuous alert, it may only notify you on the first qualifying bar. Use a repeated bar-close mode for continuous alerts if you want a notification on each qualifying bar.

1. Intrabar expectation. All alerts are bar-close gated. They will not fire during the bar — only at the bar's close. If you are watching the chart intrabar and expecting the alert to fire in real time as the condition becomes true, it will not do so until the bar confirms.

Alert fired but condition seems wrong

What you see: You received an alert saying a slot is in uptrend, but looking at the chart, the slot appears to be in downtrend (or vice versa).

Likely causes:

1. On Bar Close is off. The alert evaluated on data from the building HTF bar. By the time you checked the chart, the HTF bar's data had updated and the condition no longer holds. The alert fired on a transient state that did not survive the next update. See Alerts.

1. The chart refreshed. If you checked the chart after the next bar close, the conditions may have already changed. The alert was correct at the time it fired.

Not a bug

These are expected behaviors that commonly generate confusion or support questions.

Not a bug: Lines "step" on recent bars instead of flowing smoothly

What you see: The MA lines hold a flat value for several chart bars and then jump to a new level, rather than updating on every bar.

Why this happens: On Bar Close is on (the default). The indicator shows the previous confirmed HTF bar's value, which does not change until the next HTF bar closes. On a 1-minute chart, a 5-minute slot holds its value for five 1-minute bars, then steps. A 60-minute slot holds for sixty bars.

Why this is correct: The stepping is how you know the data is honest. Smooth lines with On Bar Close on would mean the indicator is somehow using a value that does not exist yet. The stepped appearance is the visual signature of confirmed-bar integrity — and it is the single easiest way to verify, at a glance, that your indicator is not repainting. If the lines step, the data is confirmed. If they flow, check On Bar Close. See MTF & Repainting.

Not a bug: Lines jump when toggling On Bar Close

What you see: You toggled On Bar Close on or off and the lines repositioned, especially on recent bars.

Why this happens: You are switching between two different data sources — confirmed past values vs. live building values. They produce different MA positions, especially near the right edge of the chart where the current HTF bar is still forming.

Why this is correct: The indicator is showing you the difference between the two modes. This is the repaint tradeoff made visible. See MTF & Repainting.

Not a bug: Blend line moves even though visible slot lines did not change

What you see: The blended line shifted or changed color, but the visible individual MA lines appear unchanged.

Why this happens: A hidden slot (plot hidden, still enabled with non-zero weight) changed its value or trend state. The blend reflects all enabled slots, including hidden ones.

Why this is correct: Hide Plot hides the visual, not the computation. The slot is doing exactly what you configured it to do — computing and influencing the blend from behind the scenes. If you want the slot truly removed from the blend, either disable it or set its weight to 0.

Not a bug: Slot color is solid (uptrend) but the MA line looks flat

What you see: The MA line appears to be going sideways, but its color is the solid uptrend version.

Why this happens: The trend check uses >= (greater than or equal to). A perfectly flat MA still registers as uptrend because its current value equals its value from N bars ago. The uptrend color does not require the MA to be actively rising — it only requires it to be at or above its lagged value.

Why this is correct: This is a design choice. The >= threshold means the uptrend color persists until the MA actively starts falling. The practical consequence is that the solid (uptrend) color is slightly "stickier" than the faded (downtrend) color — it holds through flat periods rather than flickering. This reduces noise during consolidation at the cost of making the uptrend color slightly less precise as a directional statement. A perfectly flat MA will show solid color. That does not mean "rising." It means "not falling yet." If you want tighter trend classification, increase the Trend Length so that the comparison spans more bars, which requires more sustained movement before the color commits.

Not a bug: "All Slots Uptrend" alert fires on every bar during a trend

What you see: You set an alert for "All MA Slots Uptrend" and receive an alert on every bar during a sustained uptrend.

Why this happens: The alignment alerts are continuous conditions. If you configure the alert in a repeated bar-close mode, they can notify on every confirmed bar while the condition holds. During a sustained trend, that can be many bars in a row.

Why this is correct: Continuous alerts are designed to confirm ongoing state. If you only want to know when alignment starts, use a webhook or external automation to detect the first occurrence. Or watch for the edge-triggered "Trend Change" alerts on individual slots, whose conditions are only true on the bar where the trend flips.