Troubleshooting

Use this page when the indicator is behaving differently from what you expected. The goal is not to hand you generic comfort. It is to help you find the specific mismatch between: - the chart timeframe - the slot geometry - the trust mode - the blend settings - your assumption about what the tool was supposed to be doing Start with the symptom closest to what you are seeing. Most issues in this indicator come from one broken relationship, not from hidden randomness. Check fit before you assume failure.

The script throws an error as soon as I add it

Likely cause

One enabled slot is violating a hard geometry rule. The most common problem is that the chart timeframe is above one of the default slot timeframes.

What to check

• Is the chart timeframe above 5, 15, or 60 while the matching default slot is still enabled?
• Is Lower TF Precision: equal to or above the slot timeframe?
• Is Window: smaller than the slot timeframe?

Fix

1. Open settings immediately.
2. Check every enabled slot's TimeFrame:.
3. Raise or disable any slot below the chart timeframe.
4. Make sure Lower TF Precision: stays below that slot timeframe.
5. Make sure Window: stays at or above that slot timeframe.

If the error disappears after those checks, the issue was geometry, not indicator failure.

The blended lines disappeared

Likely cause

The blend has no active contributors.

What to check

• Did every enabled slot get Blended Weight: 0?
• Did you disable the slots that were feeding the blend?
• Did you turn Plot Blended CVD/Signal off and assume the blend logic was gone?

Fix

1. Confirm whether the blended plot is only hidden or actually unsupported by current weights.
2. Give at least one enabled slot a non-zero blend weight.
3. Confirm that the blend returns.

If the line comes back, the issue was weighting, not missing data.

A hidden slot is still affecting the blend

Likely cause

The slot is hidden, not disabled.

What to check

• Is Enable CVD 0X still on?
• Is that slot's Blended Weight: still above 0?

Fix

If you want the slot gone from the blend, set its weight to 0 or disable it. If you only wanted less clutter, hiding it was the correct move, but the logic is still supposed to carry it. This is one of the easiest misunderstandings in the whole indicator.

A zero-weight slot is still affecting all-slot alerts

Likely cause

Weight only controls blend contribution.

What to check

• Is the slot still enabled?
• Are you looking at an all-slot alignment alert rather than the blend itself?

Fix

Disable the slot if you want it removed from alignment logic. Keep it enabled if you want the slot available for its own line or slot-specific alerts. Zero weight means "leave the blend." It does not mean "leave the script."

The chart looked different live than it did later

Likely cause

The stack was reading live-forming higher-timeframe values.

What to check

• Was On Bar Close? off?
• Were you watching a still-open higher-timeframe candle?

Fix

1. Turn On Bar Close? back on.
2. Compare the same setup in confirmed mode.
3. Decide which trust tradeoff your workflow is actually willing to carry.

If the live-forming version felt better only because it was earlier, that is not automatically a reason to keep it.

I am not seeing Session reset markers

Likely cause

Either the slot is not in Session mode, or the slot is hidden.

What to check

• Is that slot in Rolling mode?
• Is the slot hidden?
• Has the session anchor actually changed yet?

Fix

Put the slot in Session mode if you want reset markers. Keep the slot visible. Wait until the selected session anchor resets. Rolling slots do not draw reset markers by design.

The slot looks too reactive or too stubborn

Likely cause

The participation or smoothing settings are doing more work than you realized.

What to check

• Did you raise Pressure Sensitivity:?
• Did you raise Wick Weight:?
• Did you shorten CVD Length: or Signal Length:?
• Did you add master smoothing and forget the blend is now reacting later?

Fix

1. Return one setting family to defaults at a time.
2. Compare the result after each change.
3. Keep the setting that improved interpretation, not only aesthetics.

The fastest-looking line is not automatically the most trustworthy one.

The alerts are firing in a way I did not expect

Likely cause

You may be using the wrong alert family for the question you meant to ask.

What to check

• Did you want a continuing state or the moment of change?
• Are you using a slot alert when you really care about the blend?
• Are you expecting slot threshold alerts that do not exist in this build?

Fix

Use slot regime alerts for one-slot state. Use blended regime alerts for current summary state. Use Blended CVD Regime Flip for the moment of change. Use zero-line or threshold alerts only when you specifically want those events. When in doubt, re-read [Alerts](./alerts.md) and name the exact question you want the alert to answer.

The line looks bearish, but the bearish alert is not true

Likely cause

The slot CVD and slot Signal may be equal.

What is happening

The color logic and the bearish alert logic are not using identical comparisons at that exact equality edge.

Fix

Treat it as a small visual edge case, not a broken alert. Check whether the lines are equal before assuming the alert missed something. This is rare, but it is worth knowing so the chart does not talk you into the wrong story.

The alternate-ticker slot feels confusing instead of helpful

Likely cause

The slot is adding context before it has earned a role in the workflow.

What to check

• Did you compare the slot to the source market on a separate chart?
• Is the slot already blended in?
• Could you explain why that outside market belongs here?

Fix

1. Set the alternate-ticker slot to Blended Weight: 0.
2. Compare it against the source market on its own chart.
3. Only let it influence the blend after it proves useful.

If that still feels murky, the problem may be workflow fit rather than configuration.

I changed several settings and now I do not know what I am looking at

Likely cause

Too many variables changed before the last change was verified.

Fix

1. Return to one clean baseline.
2. Rebuild one choice at a time.
3. After each change, answer: what changed, why did it change, and does that actually help?

This is not a punishment for exploring. It is how you keep a flexible tool from becoming a screen full of rented conviction.

If nothing here solved it

Go back to this order: 1. [Quick Start](./quick-start.md) 2. [MTF and Repainting](./mtf-and-repainting.md) 3. [Settings](./settings.md) 4. [Visuals and Logic](./visuals-and-logic.md) Most problems with this indicator are not mysteries. They are usually one broken relationship inside timeframe geometry, trust mode, or blend logic.