Troubleshooting

Troubleshooting

This page is organized by what you see on the chart (the symptom), what is likely causing it, and what to do about it. Some of these are setup errors you can fix. Some are misunderstandings about how the indicator works. A few are genuine product limits that cannot be configured away.

The indicator will not load

Symptom: Runtime error on adding the indicator

What you see: An error message appears and the indicator does not load at all. The error references a timeframe constraint.

Likely cause: One or more slots have a timeframe set lower than the chart timeframe. For example, you are on a 15-minute chart and a slot is set to 5 minutes.

Fix: Open the indicator settings (if accessible) or remove and re-add the indicator. Check every enabled slot's timeframe. Each must be blank (inherits chart timeframe, always valid under this script's timeframe rule) or set to a value equal to or higher than the chart timeframe. The most common trigger: you configured the indicator on a 1-minute chart and then switched to a 15-minute chart without adjusting slots that were set to 5 minutes.

Why it works this way: The script explicitly blocks slot timeframes that are lower than the chart timeframe and raises a runtime error instead of continuing. That is a product rule baked into this indicator, and it is there to stop unsupported configurations from quietly producing output you might trust.

Lines look wrong or unexpected

Symptom: The MA lines look like stairs

What you see: Instead of smooth flowing lines, the MAs appear as flat steps with abrupt jumps — like a staircase.

This is not a problem. Staircase appearance is the expected behavior when a slot's timeframe is higher than the chart timeframe and On Bar Close is enabled. Each flat step represents a confirmed HTF bar's MA value. The step updates only when the next HTF candle closes.

If you are on a 1-minute chart with a 5-minute slot, you see a step every five minutes. On a 5-minute chart with a daily slot, you see a step once per trading day.

See MTF and Repainting for the full explanation of why this is the confirmed and correct behavior.

Symptom: I only see one line and the blend

What you see: The chart shows what looks like a single MA line plus the blended line, even though multiple slots are enabled.

Likely cause: Multiple slots are configured with the same timeframe, same MA type, same length, and same source. They produce identical values and their lines overlap perfectly, appearing as one.

Fix: Check the settings for each enabled slot. Make sure each slot has at least one distinguishing configuration — typically a different timeframe.

Symptom: The blend line is missing even though it is enabled

What you see: The blend toggle is on, but no blended line appears on the chart.

Check these in order:

1. Is "Hide Blended MA Plot" toggled on? This hides the line while keeping the blend active internally. Turn it off to see the line.

2. Are any slots actually enabled? If all slots are disabled, the blend has nothing to compute.

3. Do all enabled slots have weight 0? Weight-0 slots do not contribute to the blend. If every enabled slot is at weight 0, the blend computes to zero, which may plot as a flat line at the bottom of the chart or not plot at all.

Symptom: A slot's line appears at the wrong price level

What you see: A slot's MA line is far from the current price — either much higher or lower than expected.

Likely cause for a chart-native slot: The slot's MA is calculated on a very different timeframe or length than expected, producing a value that sits far from current price. Or the slot has not accumulated enough data (see "Flat or missing lines at chart start" below).

Likely cause for a cross-ticker slot: The scaling ratio may be na because the foreign ticker has no data at the requested timeframe. The line may plot at zero or at an unexpected level.

Fix: For chart-native slots, check the timeframe and length settings. For cross-ticker slots, confirm the foreign symbol is valid and has data at the configured timeframe. Try the symbol on its own chart to see if data exists.

Symptom: Flat or missing lines at the start of the chart

What you see: Lines show as na (gaps) or sit at zero for the first portion of the chart, then start plotting normally.

Likely cause: The MA needs a minimum number of bars for its lookback period. A 200-period SMA on the 1-hour timeframe needs 200 hourly bars of history before it can produce a value. Until that history accumulates, the line shows nothing.

Not a fix but a context note: This is normal behavior for all moving averages. A 200-period MA needs 200 bars of history before it can produce its first value. On high timeframes, that can require months or years of data. If you need the line to appear sooner, use a shorter length or switch to a chart with more available history. On some symbols and exchanges, TradingView's available history may not be deep enough for very long MAs on high timeframes.

Trend colors behaving unexpectedly

Symptom: Trend color is flipping on almost every bar

What you see: A slot's line changes between its uptrend and downtrend color constantly, flipping back and forth every bar or every few bars.

Likely cause: The slot's trend length is too short for the timeframe's volatility. A trend length of 1 on a fast timeframe produces color flips on nearly every bar that the MA moves at all.

Fix: Increase the trend length. A value of 3–5 is a reasonable starting point for most timeframes. Longer values produce more stable trend readings at the cost of slower response to genuine direction changes.

Symptom: The MA is flat but the trend color shows uptrend

What you see: The MA line has not moved in either direction for several bars, but the color remains the uptrend shade.

This is by design. Trend detection uses a "greater than or equal to" comparison. If the MA has not fallen compared to N bars ago, it registers as uptrend — even if it has not risen either. Flat reads as uptrend.

This prevents constant color flipping during consolidation, but it also means a sideways MA can register as uptrend longer than you might expect. See For the Geeks for the design rationale.

Symptom: Trend color changed but the line did not move

What you see: A slot's color flipped from bright to dim (or vice versa) but the line is in the same position.

Likely cause: The trend length was changed (either by you or if comparing between bars after a settings change). Or the MA value N bars ago — the comparison target — shifted because the comparison window now includes a different period.

The MA value determines line position. The trend comparison determines color. They are independent. A slot can change color without its line moving because the comparison reference changed, not the current value.

Blend behaving unexpectedly

Symptom: The blend does not sit between the visible slot lines

What you see: The blended line appears above or below all visible slot lines.

Likely cause: A hidden slot (enabled, plot hidden, non-zero weight) is contributing a value outside the range of the visible slots. Negative weights can cause this too — the current script does not clamp them, so they can push the blend outside the range you would expect from a normal weighted average.

Fix: Open Settings and check every enabled slot — including hidden ones. Note their MA values and weights, and make sure none of the weights have gone negative. The blend uses every enabled slot with a non-zero weight, not just the visible ones.

Symptom: The blend's trend color does not match what I expect from the visible slots

What you see: Two visible slots are in uptrend and one is in downtrend, but the blend shows downtrend (red).

Likely cause: The downtrend slot carries significantly more weight than the uptrend slots. The blend's trend is a weighted vote, not a majority count. One high-weight slot can outvote two low-weight slots.

Fix: Check the weight distribution. If the result is unintended, adjust the weights so that no single slot dominates the vote in a way that does not match your priorities.

Symptom: The blend trend flipped but no individual slot changed

What you see: The blend color changed from lime to red (or vice versa) but every individual slot's color stayed the same.

Possible causes:

1. A hidden slot changed trend state without being visible.

2. A slot was enabled or disabled, changing the set of voters.

3. A weight was adjusted, tipping the balance of the vote without changing any slot's direction.

Investigation: Check recent settings changes, hidden slot states, and whether any slot was recently toggled. The blend's trend is a vote, and small changes in the electorate can flip the outcome.

Alert issues

Symptom: Continuous alert fires on every bar

What you see: You set up an "Is Uptrend" or "Is Downtrend" alert and it fires a notification on every single bar close.

This is expected behavior. Continuous alerts fire on every bar where the condition is true. If the slot has been in uptrend for 200 bars, you get 200 notifications (one per bar close).

Fix: If you want notification only when the trend flips, use the Trend Change alert condition instead. It fires once at the moment the trend state changes, then goes silent until the next change.

Symptom: Alignment alert fires but I can see a slot that disagrees

What you see: The "All MA Slots Uptrend" alert fires, but one slot on the chart appears to be in downtrend.

Possible cause: The disagreeing slot may be disabled (not counted toward alignment) while its line is still visible from a previous configuration state. Or the slot may have flipped between the bar that triggered the alert and the moment you looked at the chart.

Fix: Check the Data Window for the Active Uptrend Count and Active Downtrend Count at the bar where the alert fired. Confirm which slots were enabled at that time.

Live vs. historical behavior

Symptom: My backtest results do not match live performance

Likely cause: One or more slots have On Bar Close turned off. The backtest replays history using final HTF bar values, while live trading sees intermediate values during the forming HTF candle. The backtest gives the indicator information it would not have had in real time. This is the most common cause of "looks great on history, mediocre live" with any multi-timeframe indicator.

Fix: For reliable backtesting, keep On Bar Close on for every slot that contributes to the decision logic. If you have already backtested with some slots unconfirmed, those results should be discarded — they reflect a version of history that never existed during live conditions. See MTF and Repainting for the full explanation.

Symptom: A slot's line was moving during a live session but the history shows it as flat

Likely cause: The slot has On Bar Close turned off. During the live session, the line updated continuously as the HTF candle built. After the candle closed, history shows only the final value, which appears as a single flat step. The intermediate movement is not recorded.

This is the repainting tradeoff. It is not a bug. The history always shows the final answer. The live experience included the preliminary answers. See MTF and Repainting.

When to ask for help

If your issue is not covered here, consider:

• Checking the Settings page for details on specific parameters

• Checking MTF and Repainting for any repaint-related confusion

• Checking Limitations and Trust Boundaries to confirm whether what you are seeing is a limitation rather than a bug

If the indicator is producing behavior that genuinely does not match anything described in this manual, the issue may require support. Before reaching out, note the chart symbol, chart timeframe, the slot configuration involved, and what you expected versus what you saw. Concrete details make it possible to diagnose; "it looks wrong" does not. Check the Axiom community channels if they are available for your subscription tier.