Troubleshooting

Use this page when the indicator is doing something you do not expect. The goal is not to hunt for exotic edge cases first. The goal is to check the common, high-impact causes in the right order so you do not spend ten minutes blaming the wrong thing. Start with the symptom that looks closest to your chart.

The fastest diagnostic order

1. Are the enabled slot timeframes valid on this chart?
2. Which slots are actually enabled right now?
3. Which of those slots still have non-zero blend weight?
4. Are any active slots hidden?
5. Are any active slots using Optional Ticker: or mixed On Bar Close? posture?

That order solves more problems than most deeper settings checks.

Symptom: the script throws an error as soon as I add it

Likely cause:

• one enabled slot timeframe is lower than the chart timeframe

What to check:

• compare the chart timeframe to DC 01, DC 02, and DC 03
• remember the shipped defaults are 5, 15, and 60

How to fix it:

• raise the conflicting slot timeframe
• or disable that slot

Why this happens:

• the current build blocks lower-than-chart enabled timeframes by design

Symptom: a slot disappeared, but the blend still looks influenced by it

Likely cause:

• the slot is hidden, not disabled

What to check:

• Enable DC 0X
• Hide DC 0X Plot
• Blended Weight:

How to fix it:

• disable the slot if you want it fully removed
• or set its weight to 0 if you only want it out of the blend

Why this happens:

• hiding removes the drawing only
• hidden weighted slots can still shape the blend

Symptom: I set a slot weight to 0, but it still matters somewhere

Likely cause:

• zero weight only removes blend influence

What to check:

• does the slot still plot
• is the slot still firing slot-level alerts
• is the slot still part of All DC Slots Above Basis or All DC Slots Below Basis

How to fix it:

• disable the slot if you want it fully gone

Why this happens:

• zero weight does not disable slot logic, slot plots, or alignment logic

Symptom: the blended channel dropped toward zero or stopped meaning anything

Likely cause:

• every enabled slot now has Blended Weight: set to 0

What to check:

• list the enabled slots
• confirm whether any of them still has non-zero blend weight

How to fix it:

• restore non-zero weight to the slots that truly belong in the summary
• or turn the blended channel off and work from the slot-level view if you do not want a summary layer right now

Why this happens:

• the current build leaves the blended output without a meaningful contributor set when every enabled slot weight is 0

Symptom: the blended channel looks wrong or unhelpful

Likely causes:

• the contributing weights no longer match the workflow
• a hidden slot is still shaping the blend
• the contributor set now mixes symbols, basis families, or timing postures more than you intended
• every enabled slot weight has been set to 0

What to check:

• list the enabled slots
• mark which ones still have non-zero weight
• check whether any contributor is using another ticker
• check whether contributors are confirmed, live-forming, or mixed

How to fix it:

• simplify the contributor set
• reset uncertain slots to 0 weight
• return to a same-symbol confirmed baseline if the blend no longer feels explainable

Why this happens:

• the blend is a weighted summary of slot outputs, not an independent channel

Symptom: some slots update sooner than others

Likely cause:

• the stack is using mixed On Bar Close? posture

What to check:

• each active slot's On Bar Close? setting

How to fix it:

• make the stack fully confirmed if you want steadier behavior
• or keep one live-forming slot only and treat it as exploratory

Why this happens:

• On Bar Close? is per slot in this build

Symptom: the alternate-ticker slot looks strange or too neat

Likely causes:

• the slot is being read as native price instead of remapped context
• the outside market is being given blend influence before it was verified

What to check:

• which slot is using Optional Ticker:
• whether that slot still has Blended Weight: at 0 or above
• whether you compared it to the source market on a separate chart

How to fix it:

• return that slot to 0 weight first
• verify it against the source market directly
• decide whether the outside context is helping before you let it steer the blend

Why this happens:

• the feature is built for readable context, not for direct price equality

Symptom: the basis line changed, but the channel edges did not move the same way

Likely cause:

• you changed Basis MA Length: or Type:

What to check:

• the slot's Length:
• the slot's Basis MA Length:
• the slot's Type:

How to fix it:

• decide whether the basis behavior is still useful for your workflow
• reset Type: to SMA or reduce basis tuning if you want a simpler read

Why this happens:

• the basis is a smoothed midpoint
• the outer bounds stay anchored to the raw Donchian lookback

Symptom: alerts feel too quiet

Likely causes:

• you chose a state-change alert but expected a continuing reminder
• the chart bar has not closed yet
• the slot you care about is disabled or not contributing the way you thought

What to check:

• whether you created Basis Change or Is Above/Below Basis
• whether the chart bar actually closed
• whether the slot is enabled and in the mode you intended

How to fix it:

• switch to a state alert if you need ongoing condition checks
• keep using change alerts if you only want the flip

Why this happens:

• state alerts and change alerts solve different jobs
• all alert conditions are chart-bar-close gated

Symptom: alerts feel noisy or misleading

Likely causes:

• the stack is too wide for the workflow
• blend contributors changed without you noticing
• the alert is speaking for a live-forming slot you were treating like confirmed structure

What to check:

• active slot count
• non-zero blend contributors
• per-slot timing posture

How to fix it:

• reduce the stack
• keep core slots confirmed
• remove unnecessary alert families until the read is stable again

Why this happens:

• alerts only inherit the clarity of the stack behind them

Symptom: full-stack alignment triggered, but the setup still looks weak

Likely cause:

• alignment is narrower than conviction

What to check:

• whether the active slots actually deserve equal authority
• whether the contributors share the same timing posture
• whether any contributor is remapped from another ticker

How to fix it:

• treat alignment as a prompt, not as approval
• go back to slot-by-slot reading before you act

Why this happens:

• All DC Slots Above Basis and All DC Slots Below Basis only tell you where active slots sit relative to their basis lines

If you want the cleanest reset

When the stack feels too muddy to debug one setting at a time, reset to:

• DC 01, DC 02, and DC 03 only
• same symbol on every active slot
• On Bar Close? on for every active slot
• one basis family across the active slots
• clear non-zero blend contributors

That reset is not starting over. It is how you get back to a stack you can explain, which is how real troubleshooting becomes possible again.