Troubleshooting

Use this page when the indicator is doing something you do not trust, do not expect, or can no longer explain. The fastest way through troubleshooting is to start with the symptom, reduce the stack, and test one moving part at a time. Most problems here come from slot legality, timing posture, blend participation, or alert expectations.

Triage in this order

When the pane feels wrong, check these in order before you do anything more exotic:

1. slot legality
2. timing posture
3. blend participation
4. alert family expectations

That order catches most failures without turning debugging into guesswork.

Symptom: the script throws an error when I add it

Likely cause

One of the enabled slots is illegal on the current chart, or one slot has Fast Length: greater than or equal to Slow Length:.

What to check

• compare every enabled TimeFrame: to the chart timeframe
• confirm Fast Length: is still below Slow Length: on each enabled slot

Fix

• raise or disable any enabled slot that sits below the chart timeframe
• restore a valid fast-versus-slow relationship on the broken slot

Symptom: the blend disappeared

Likely cause

Every active contributor has Blended Weight: at 0, or the remaining blend contributors are invalid.

What to check

• whether at least one enabled slot still has non-zero weight
• whether that slot is valid on the chart timeframe

Fix

• give at least one valid active slot a positive weight
• fix any slot legality issue before expecting the blend to return

Symptom: a slot is not visible, but it still seems to matter

Likely cause

The slot is hidden, not disabled.

What to check

• whether Enable MACD XX is still on
• whether only Hide MACD XX Plot was changed
• whether the slot still has non-zero blend weight or still counts toward alignment

Fix

• disable the slot if you want it fully out
• leave it hidden only if you still want the slot alive for logic, alerts, or blend participation

Symptom: I set weight = 0, but the slot still affects alerts or alignment

Likely cause

Zero weight removes a slot from the blend only.

What to check

• whether the slot is still enabled
• whether you are looking at slot alerts or alignment rather than the blend

Fix

• disable the slot if you want it out of slot logic and alignment too
• keep it at zero weight only when you want a diagnostic slot outside the blend

Symptom: one slot moves sooner than the others

Likely cause

That slot is using a different TimeFrame:, a different ticker, or a different On Bar Close? posture.

What to check

• the slot TimeFrame:
• the slot Optional Ticker:
• whether On Bar Close? is different from the other active slots

Fix

• normalize those settings across the comparison slots if you want a cleaner baseline
• keep the difference only if it serves a job you can explain

Symptom: the blend looks calmer than the slot stack

Likely cause

One slot may be dominating the weight mix, or master smoothing may be calming the summary after the blend is built.

What to check

• the active slot weights
• whether Enable Master Smoothing is on
• whether some active slots are outside the blend because their weight is 0

Fix

• reduce weight concentration
• turn master smoothing off and inspect the unsmoothed blend
• compare blend state with alignment before trusting the calmer read

Symptom: alerts are not firing when I expected

Likely cause

The condition has not been met on chart bar close, or you are expecting a different alert family than the one you set.

What to check

• whether the chosen alert is a state alert or an event alert
• whether the chart bar has actually closed
• whether the slot is enabled
• whether you expected blend behavior from a slot alert, or alignment behavior from a blend alert

Fix

• choose the alert family that matches the question you are asking
• wait for chart bar close before expecting an alert
• verify the condition on-chart before assuming the alert is broken

Symptom: I cannot find per-slot regime-flip alerts

Likely cause

They are not part of the implemented alert surface in the current documented build.

What to check

• the alert picker itself

Fix

• use the implemented slot bullish and bearish state alerts instead
• use Blended MACD Regime Flip if the summary-level change event is what you actually need

The script comments mention per-slot flips, but the current code does not expose them as alert conditions.

Symptom: the outside ticker feels convincing, but I cannot explain why

Likely cause

The alternate-symbol slot is adding persuasion faster than it is adding usable context.

What to check

• what job that outside symbol is supposed to serve
• whether the slot is already influencing the blend
• whether the same workflow still works without the outside slot

Fix

• set the outside slot weight back to 0
• compare the outside market on a separate chart
• keep the slot only if it adds one clean layer of context you can name

Symptom: the rails feel like automatic reversal signals

Likely cause

The stretch markers are being read as commands rather than as context.

What to check

• how the same threshold behaves across different timing postures
• whether the active slots are agreeing or whether one slot is doing most of the work
• whether the market context is supportive or only visually stretched

Fix

• treat overbought and oversold as stretch information inside this tool's bounded language
• use the rails alongside slot state, blend state, and workflow context rather than by themselves

A good reset procedure

If the whole pane feels suspect, reset in this order:

1. keep only the first three same-symbol slots active
2. keep their weights equal
3. turn On Bar Close? on for all three
4. leave master smoothing off
5. verify the baseline again before reintroducing anything custom

That reset solves more confusion than trying to debug a fully customized ten-slot stack all at once.

Visual placeholder: Troubleshooting table showing the top six symptoms, the exact setting to inspect first, and the shortest corrective action.