Troubleshooting

Symptom

Cause

Category

Fix

The indicator throws an error message on load and refuses to plot

A slot's timeframe is set to a period shorter than the chart timeframe. The indicator enforces a "slot TF must be >= chart TF" rule at runtime.

Misconfiguration

Open settings and find the slot named in the error message. Change its timeframe to a value equal to or greater than the chart timeframe, or set it to empty ("") to default to the chart timeframe.

The error appeared after I switched the chart to a higher timeframe

Same cause — a slot that was valid on the old chart timeframe is now below the new chart timeframe.

Misconfiguration

Adjust the offending slot's timeframe to match or exceed the new chart timeframe. If you frequently switch chart timeframes, consider setting lower slots to the chart timeframe ("") so they always adapt.

Symptom

Cause

Category

Fix

The bands are flat and only update every N bars

On Bar Close is on, and the slot's timeframe is higher than the chart timeframe. The bands update once per HTF candle close, not every chart bar. On a 1-minute chart with a 60-minute slot, the bands update once per hour.

Expected behavior

This is not a bug. It is the stability guarantee. The flat behavior between HTF candle closes means the bands are showing confirmed values, not provisional ones. If you want live updates, you can turn On Bar Close off — but understand the tradeoff described in MTF & Repainting.

The bands have not moved in a very long time

The slot is set to a very high timeframe relative to the chart (e.g., a weekly slot on a 1-minute chart). The bands update once per week.

Expected behavior

Consider whether a weekly BB on a 1-minute chart is giving you useful information. It provides weekly structural context, but it updates so infrequently that it is effectively a fixed reference for most of the trading week.

One slot's bands are flat while others are moving

Each slot has its own timeframe. The flat slot has a higher timeframe than the moving ones, so it updates less frequently.

Expected behavior

No fix needed. This is the multi-timeframe layering working as intended.

Symptom

Cause

Category

Fix

Cross-ticker bands are missing (no lines drawn)

The Optional Ticker symbol string is invalid, or the symbol has no data for the requested timeframe on TradingView.

Misconfiguration

Check the ticker string. TradingView requires exact symbol format (e.g., NASDAQ:AAPL, or just AAPL on some data feeds). Try typing the symbol into a TradingView chart's symbol search to confirm it resolves.

Cross-ticker bands appear but shift unexpectedly

The close ratio between the chart symbol and the reference symbol changed. The scaling multiplier updates per bar, so when the ratio moves, the projected bands move even if the reference symbol's actual BB did not change.

Expected behavior / Real limit

This is how the scaling works. The projection is approximate and ratio-dependent. If the two symbols diverge significantly, the scaling drift increases. This is a fundamental property of the close-ratio approach — not a bug. See For the Geeks for more on the scaling mechanics.

Cross-ticker bands do not match the reference symbol's actual BB

The cross-ticker bands are the reference symbol's BB values multiplied by the close ratio, not the raw BB values. The proportional structure is preserved, but the absolute values differ.

Expected behavior

This is correct. You are seeing the reference BB projected into the chart's price space, not the reference BB itself. To compare, open a separate chart of the reference symbol with a standard BB at the same settings — the band shapes should be similar, but the price levels will differ.

Symptom

Cause

Category

Fix

The blended band does not match what I expect from the visible slots

A hidden slot (plot turned off but slot still enabled with weight > 0) is contributing to the blend.

Misconfiguration

Open settings and check whether any hidden slots have non-zero weights. Either set the hidden slot's weight to 0 (to exclude it from the blend) or disable the slot entirely.

The blended band tracks one slot almost exactly

Only one slot has significant weight, or only one slot is enabled. The blend is a weighted average — if one contributor dominates, the blend follows it.

Expected behavior

If you want a more balanced blend, adjust weights so multiple slots contribute meaningfully.

The blended band sits at the bottom of the chart or looks broken

All enabled slots have weight set to 0. The blend has no contributors and computes a zero value.

Misconfiguration

Set at least one enabled slot's weight to a value greater than 0.

The blended band is very close to one slot even though weights look equal

Equal weights still average the raw upper, basis, and lower values. If one slot's plotted values sit much farther from the others, the blend can appear closer to that slot even without a weight imbalance.

Expected behavior

This is arithmetic, not a bug. Check the actual slot values rather than the visual spacing alone. If you want a different composite, adjust weights or remove the outlier slot from the blend.

Symptom

Cause

Category

Fix

The chart is unreadable with too many overlapping bands

Too many slots are enabled. Each slot draws three lines (upper, basis, lower), so 5 slots means 15 lines plus the blended band.

Misconfiguration

Disable slots you do not actively need. Start with 2–3 and add more only when each one serves a specific purpose.

I want some slots to influence the blend but not clutter the chart

This is what the Hide Plot setting is for — it removes the slot's visual lines while keeping the slot active for blend contribution.

Configuration option

Turn on Hide Plot for the slots you want to contribute silently. Remember that hidden slots still affect the blend — this is a feature, not a side effect.

The blended band dominates the chart visually

The blended band defaults to line width 3, which is heavier than the per-slot default of 2. Combined with the red fill, it sits on top of everything.

Configuration option

Reduce the blended line width in settings, or hide the blended band if you prefer to read the individual slots without the synthesis layer.

Symptom

Cause

Category

Fix

An alert fires repeatedly on every bar

The alert condition is true on every confirmed chart bar. For example, "BB 01 Is Above Basis" fires on every bar where price is above Slot 1's basis — not just the first bar where it crossed.

Expected behavior

TradingView alerts fire whenever the condition is true, unless you configure them as "Once Per Bar Close" or "Once Per Bar." If you want an alert only on the transition (the cross), use the "Basis Change" alert instead.

The basis-change alert fired but I do not know which direction

The "Basis Change" alert fires on any flip — above-to-below or below-to-above. It does not encode direction.

Expected behavior

Pair the basis-change alert with the above/below alerts, or check the chart when the alert fires to see the current positioning.

Alignment alert fired but broke immediately

Alignment is a point-in-time observation. "All above basis" fired because every enabled slot had price above basis on that confirmed bar. On the next bar, one slot may have crossed below, breaking alignment.

Expected behavior

Alignment is a filter, not a durable state. Use it to flag moments of agreement, but do not expect the agreement to persist.

Alerts seem delayed compared to what I see on-chart

All alerts fire on confirmed (closed) bars only. If you are watching the chart mid-bar, you may see a condition become true before the bar closes — but the alert will not fire until the bar is confirmed.

Expected behavior

This is the confirmed-bar gating working as designed. The alert waits for the bar to close to ensure the condition is not a mid-bar fluctuation.