Troubleshooting

Written By Axiom Admin

Last updated About 1 month ago

Troubleshooting

This page is organized by symptom — what you see that looks wrong — followed by the likely cause and what to do about it. Some of these are setup errors with quick fixes. Some are expected behavior that looks broken if you do not know what to expect. Some are genuine edge cases in the tool's design. The fix column distinguishes between them so you can tell the difference before you start changing settings.

Start with the diagnostic rule at the bottom of this page if your issue does not match any of the specific symptoms below. It will help you narrow down whether you are looking at a settings problem, a market event, or a data issue.

Errors and failures

Symptom	Likely cause	What to do
The indicator shows an error message on load	A slot's timeframe is set lower than the chart timeframe, which trips this script's runtime guardrail.	Open settings and set every slot's TimeFrame to a value at or above your chart timeframe. If you are on a daily chart, all slots must be daily or higher. If you are on a 15m chart, no slot can be below 15m.
The indicator loads but shows no lines	All slots are disabled, or all slots are hidden.	Check that at least one slot has "Enable" checked and "Hide Plot" unchecked. Also check that the Blended BB is enabled if you expect to see the blend.
Only some slots are visible	The missing slots may be disabled or hidden.	Open settings and check the Enable and Hide Plot toggles for each slot. Remember that "Hide Plot" removes visual lines but does not disable the slot — it may still be computing and contributing to the blend.

Unexpected visual behavior

Symptom	Likely cause	What to do
The bands look flat or stepped instead of smooth	This is normal higher-timeframe behavior. When a slot's timeframe is higher than the chart's, the values update only when a new HTF bar closes. Between closes, the values hold constant.	No fix needed — this is the expected behavior with On Bar Close on. If you want smoother updates, you can turn On Bar Close off in PU Settings, but read MTF & Repainting first to understand the tradeoff.
The blended band does not match the visible individual slots	A hidden slot is still enabled and contributing to the blend. The blend includes all enabled slots, regardless of plot visibility.	Open settings. Check whether any slot has "Hide Plot" on but "Enable" also on. If so, that slot is feeding the blend invisibly. Either disable the slot or set its weight to 0 if you want it out of the blend.
The blended band looks narrower than all individual bands	This is expected in normal positive-weight setups. The blend is a weighted average, and an average of different-width bands is typically narrower than the widest and wider than the narrowest.	No fix needed. The blend is a summary, not a super-envelope. It compresses the individual readings into a composite.
The blended band jumped when I changed settings	Any change to slot enable/disable state, weights, timeframes, or MA types recalculates the blend immediately.	Check what you changed. The blend is reactive to configuration. If the jump surprised you, it is usually because you forgot which settings feed the blend.
The bands look different after I toggled On Bar Close	Expected. Toggling On Bar Close switches between confirmed (previous HTF bar) and building (current HTF bar) values. Historical bars will show different values because the data source changed.	This is correct behavior. The chart's past representation depends on this setting. See MTF & Repainting for the full explanation.
The blended band contracted toward zero unexpectedly	One slot may have resolved to `na`, and the script then zero-filled that slot on the way into the blend. Cross-ticker data issues are one possible cause.	Check whether any foreign ticker is invalid, closed, or missing data. If you find a likely culprit, either disable that slot, set its weight to zero, or accept that the blend is reflecting partial data during that period. See For the Geeks for the full explanation.
All three slots show nearly identical bands	All slots are set to the same timeframe, or the timeframes are too close together to produce meaningfully different readings.	Set each slot to a different timeframe that represents a distinct scale. A 5m/6m/7m stack is effectively three copies of the same data. A 5m/15m/60m stack gives three distinct views.

Alert issues

Symptom	Likely cause	What to do
An alert does not fire even though the condition appears true on the chart	The alert fires only on confirmed (closed) bars. If the condition is true on the building bar but the bar has not closed yet, the alert will not fire until bar close.	Wait for the current bar to close. If the condition is still true at bar close, the alert should fire. If the condition reversed before bar close, the alert correctly did not fire.
An alert fires but the condition does not match what I see on the chart	Three common causes: (1) You changed the indicator's settings after the alert was created — TradingView alerts are bound to the configuration at creation time, not the current settings. (2) You are looking at a different timeframe or symbol than the one the alert monitors. (3) The condition was true at bar close (when the alert fired) but has already reversed on the current building bar by the time you check.	Check the alert's configuration in TradingView's alert manager. Confirm you are on the same symbol and timeframe. If the indicator settings changed, delete and recreate the alert with the current settings.
The "All Slots Above/Below Basis" alert is not firing even though most slots agree	This alert requires unanimous agreement from all enabled slots. If even one slot disagrees, the alert does not fire.	Check every enabled slot's basis position. The alert fires only when every active slot has price on the same side of its basis. A 2-out-of-3 agreement does not count.
I am getting too many state alerts (Above/Below Basis)	State alerts fire on every qualifying bar, not just the first one. If price stays above a slot's basis for 50 bars, the "Above Basis" alert fires 50 times.	If you only want to know about transitions, use the "Basis Change" alert instead. It fires once when the regime flips.

Cross-ticker issues

Symptom	Likely cause	What to do
The cross-ticker slot's bands appear at an unexpected level	The price-space scaling adjusts the foreign bands based on the price relationship between the two instruments. If the instruments have very different price levels, the scaling amplifies or compresses accordingly.	This is expected behavior. Compare the foreign slot's bands to a standalone BB on the foreign ticker's own chart to verify the behavior is consistent. See For the Geeks for how the scaling works.
The cross-ticker overlay seems to move independently of the foreign symbol	The scaling ratio changes as both instruments' prices change. If the instruments are not well-correlated, the ratio can shift in ways unrelated to either instrument's volatility.	This is a limitation of ratio-based scaling. It works best on correlated instruments. See Limitations & Trust Boundaries for guidance on when cross-ticker overlays are and are not useful.
The cross-ticker slot shows no data	The foreign symbol may be invalid, the market may be closed, or the data feed may be unavailable.	Check the symbol name in the Optional Ticker field. Verify the foreign market is currently in session. Try the symbol on its own chart to confirm data availability.

When to check settings vs. when to check the market

This is the single most useful diagnostic principle for this tool. Most confusion comes from not knowing whether the chart changed because of the market or because of the configuration.

The rule: If the behavior changed after you modified a setting, the setting caused it. If the behavior changed on its own while you were watching, the market may have caused it — or one slot may have resolved differently than it was a moment ago.

Blend shifted? Check settings first. Did you enable, disable, or hide a slot? Change a weight? Switch a timeframe? The blend reflects configuration changes immediately. If the blend jumped and you touched the settings panel in the last few seconds, the setting is almost certainly the cause.
Individual slot shifted? Check the market. Individual slots respond to price action on their configured timeframe. If one slot's bands widened while the others stayed stable, volatility increased on that slot's timeframe. This is the tool working correctly.
Everything shifted at once? Check On Bar Close. If you toggled On Bar Close, all slots and the blend change simultaneously because the data source switched between confirmed and building values. This is the most dramatic single-setting change in the tool.
Blend contracted toward zero? Check unresolved slots. Cross-ticker data gaps are one possible cause, but the broader issue is that one slot may have resolved to na and then been zero-filled into the blend. See the zero-fill section in For the Geeks.
Not sure what changed? Disable all slots except one. If that slot looks correct, re-enable the others one at a time. The slot that changes the behavior when re-enabled is the one to investigate.