Troubleshooting

Use this page when the chart is behaving in a way that feels wrong, confusing, or harder to trust than it should. The goal is not to memorize edge cases. The goal is to move from symptom to likely cause quickly, then verify the fix before you keep going. Most problems here come from one of three places: the chart timeframe does not fit the active slots, the visible chart no longer matches the active logic, or the stack has become harder to explain than it looks.

Fast symptom table

Symptom: the indicator errors immediately on load

Likely cause

At least one enabled slot timeframe is below the current chart timeframe. The default stack starts at `5 / 15 / 60`, which is fine on a one-minute or five-minute chart, but not on every chart.

What to do

1. Open settings immediately.
2. Check `TimeFrame:` for each enabled slot.
3. Raise or disable any slot that sits below the chart timeframe.
4. Confirm the chart now loads cleanly before changing anything else.

Verify the fix

You should see the chart draw the intended envelopes without the runtime error returning.

Symptom: I hid a slot, but it still seems to matter

Likely cause

`Hide BB 0X Plot` only removes the drawing. It does not disable the slot.

What to do

• If you want the slot gone from logic, turn off `Enable BB 0X`.
• If you only wanted less clutter, keep it hidden and accept that it still matters internally.

Verify the fix

Toggle `Enable` off and confirm whether the blend or alignment changes. That tells you the slot was active, not merely visible.

Symptom: the blend looks meaningless or flat after weight changes

Likely cause

One of three things usually happened:

• you zero-weighted the contributor you were really relying on
• you assumed hidden slots stopped contributing
• all active slot weights are now `0`

What to do

1. List the enabled slots.
2. Check which ones still have non-zero `Blended Weight:`.
3. Decide whether the blend still has any meaningful contributors.

Verify the fix

Move one contributor from `0` back to a non-zero weight and confirm the blend becomes informative again.

Symptom: different slots update at different times

Likely cause

The active slots are not sharing one timing posture. Because `On Bar Close?` is per slot, one slot can stay confirmed while another is allowed to move sooner inside an unfinished higher-timeframe candle.

What to do

• Check `On Bar Close?` on each active slot.
• Decide whether the mixed timing is intentional.
• If it is not intentional, bring the active stack back to one consistent posture.

Verify the fix

Watch the stack during an unfinished higher-timeframe candle and confirm the slots now behave the way you expected.

Symptom: the alternate-ticker slot looks strange

Likely cause

The slot is being remapped into the chart's price neighborhood. It is not supposed to look like raw price from the other market.

What to do

• Put that slot at `0` blend weight first.
• Open a second chart with the source market.
• Compare the broad structure, not the literal price level.

Verify the fix

You should be able to say what that outside market is adding to the read without pretending the prices are directly interchangeable.

Symptom: the chart still looks familiar, but one slot behaves differently than expected

Likely cause

That slot may be using a different `Type:` than the rest of the stack. Once `Type:` moves away from `SMA`, the layout still looks like a Bollinger envelope, but the basis behavior underneath it has changed.

What to do

• Check `Type:` on the active slots.
• Keep one diagnostic slot on the new basis family and the rest on the old one until the difference is understandable.

Verify the fix

You should be able to explain what changed about the slot besides its appearance.

Symptom: alerts wait for the close even though some slots are live-forming

Likely cause

These are two different timing layers:

• `On Bar Close?` changes whether a slot reads confirmed or live-forming higher-timeframe values
• alerts still wait for the chart bar to confirm

What to do

Keep those two ideas separate. If you need earlier workflow feedback, decide whether live-forming slot behavior actually helps you. Do not expect the alert gate itself to change.

Verify the fix

Watch the same chart live and confirm: the slot values can move earlier with `On Bar Close?` off and the alert condition still waits for the chart bar to close.

Symptom: alerts keep firing when I only wanted the moment of change

Likely cause

You probably chose an ongoing state alert such as `Is Above Basis` or `Is Below Basis` when you really wanted a transition alert.

What to do

• Use `Basis Change` for slot or blended basis flips.
• Use the blended cross alerts when you want the moment price crosses a blended boundary.

Verify the fix

Once the new alert is set, check whether it now arrives only when the condition changes instead of while the condition simply remains true.

Symptom: I enabled more slots and the chart became harder to trust

Likely cause

The stack grew faster than your mental model of it.

What to do

• Return to fewer active slots
• same-symbol context only
• one basis family across the core stack
• consistent timing posture
• one or two meaningful blend contributors

Verify the fix

You should be able to explain each active slot in one short sentence again.

When simplifying is the real fix

If several symptoms are showing up at once, the best fix is often not another adjustment. It is a simpler stack.

Return to:

• the default `5 / 15 / 60` same-symbol ladder
• confirmed slots only
• no alternate ticker
• one familiar basis family
• That version is easier to verify, and it usually reveals whether the extra complexity was helping or only adding fog.

If simplification fixes the problem, keep the simpler version long enough to understand why.