Troubleshooting

Symptom first, then a likely cause, then the check to run, then the fix. Ordered roughly by how often each complaint shows up rather than by category. When a symptom traces back to a deeper misread pattern, this page points at the right section of Limitations & Trust Boundaries instead of re-teaching the concept here — the trust-boundaries page is the canonical location for those explanations.

The first move when something looks wrong is almost always to open the inputs dialog and audit the configuration before blaming the tool. Two-thirds of "this pane is broken" reports resolve at that step. The other third are misreads of correct behavior that the next page in the chain explains.

Quick symptom index

1. The pane is empty or not rendering

Likely cause. Either no slots are enabled, or every enabled slot has a weight of zero and Plot Blended Fast/Slow is off, or the symbol has insufficient history for the baseline MA to compute.

Check. Open the inputs dialog. Count the number of slots with Enable = true. Count how many of those have a Blended Weight above zero. Confirm Plot Blended Fast/Slow is on unless you deliberately disabled it.

Fix. Enable at least one slot. If you want a blended line, make sure at least one enabled slot has positive weight. On symbols with very short history, wait for enough bars to accumulate for the longest baseline length to compute.

2. Values look stuck at 0 or at 100 for long stretches

Likely cause. Boundary pinning from ATR Sensitivity set too high for the current regime, an ATR Length too short to compute a useful volatility scale, or a genuinely extreme market that is stretching faster than ATR can adapt.

Check. Note the current ATR Sensitivity and ATR Length. Compare the pane's behavior here against a quieter section of history on the same chart. Was the pane pinning there too, or only now? If only now, the pinning is regime-driven; if always, the settings are too aggressive for this instrument in general.

Fix. Move ATR Sensitivity back toward 1.0 first. If the pane still pins, extend ATR Length — a longer window stabilizes the volatility scale so a short volatility spike does not compress the normalization. If both are at defaults and the pane still pins, the move is genuinely outside what ATR normalization covers in this regime, and the pane cannot tell you more than "the reading is saturated." Do not interpret a pinned reading as intensity while you diagnose. See the boundary pinning section of Limitations & Trust Boundaries for the full reasoning.

3. A slot's color is the opposite of what I expected on first load

Likely cause. First-bar fallback. Until a slot's slow line has enough history to be defined, the slot falls back to comparing fast against 50 to determine color. This is transient.

Check. Wait for enough bars to pass that the slow length has matured. For the default Slow Length 3, this is almost immediate. For longer slow lengths, it takes proportionally longer.

Fix. Nothing to do except wait. If the fallback behavior is a problem in your workflow, shorten the slot's Slow Length or accept that the first few bars after load can carry a fallback color. This is called out in Visuals & Logic as well.

4. The blend barely moves while price is moving a lot

Likely cause. Either the enabled slots are heavily weighted toward higher-timeframe slots that are slow by design, or master smoothing is pulling the blend behind, or ATR Sensitivity is flattening the reading.

Check. Inspect slot weights. Disable master smoothing temporarily and see how the blend behaves. Confirm ATR Sensitivity is at 1.0 unless you set it otherwise.

Fix. Rebalance weights if higher-timeframe slots are dominating past what you want. Reduce master smoothing length or disable it during diagnosis. Reset ATR Sensitivity to 1.0 and retune only if you have a reason to leave it elsewhere.

5. The slot says one thing, the chart says another

Likely cause. Either you are looking at a cross-asset slot (the slot's Optional Ticker is set) or the slot's timeframe and MA settings are such that its story differs from the chart-instrument's chart-timeframe story — which is what MTF slots are for in the first place.

Check. Open the slot in the inputs dialog. Is Optional Ticker set? If yes, the slot is reporting stretch on the ticker, not on the chart. If no, what is the slot's timeframe and what is the chart timeframe? A higher-timeframe slot can legitimately disagree with a chart that is reacting to intrabar action.

Fix. If the slot is cross-asset and you did not want that, clear the ticker. If the disagreement is between a higher-timeframe slot and the live chart, the disagreement is expected behavior — the slot is carrying context that the chart-timeframe read does not.

6. My alert never fires even though the state was clearly met

Likely cause. Every alert condition in this script is gated by bar close. If the state existed intrabar but was no longer true at the close of the bar, the alert does not fire.

Check. Look at the close of the bar you expected the alert on. Was the reported state true at that close? If the bar closed in a different state than you observed during the bar, the alert correctly did not fire.

Fix. Either accept bar-close evaluation as the honest behavior, or adjust your expectation to match. There are no intrabar alert variants in this script. See Alerts.

7. The pane behaves differently on this chart timeframe than another

Likely cause. Slot timeframes are bounded below by the chart timeframe. When the chart timeframe rises above a slot's configured timeframe, the script raises a named runtime error instead of drawing that lower-timeframe slot. Equal-to-chart slots are valid, but they are chart-timeframe reads rather than higher-timeframe context.

Check. For each enabled slot, compare the slot TF to the current chart TF. If any slot TF is below the chart TF, fix it before reading the pane. If any slot TF is equal to the chart TF, the slot can compute but is not giving you higher-timeframe context.

Fix. Either change the chart timeframe back to one where your slot stack is valid, or adjust the slot timeframes to sit at or above the new chart TF. For real MTF context, keep the slot timeframes above the chart timeframe. See MTF & Repainting for the rule in full.

8. The pane values changed after the bar closed

Likely cause. A slot has On Bar Close? set to OFF. That slot reads the live higher-timeframe bar and its value moves until the bar closes. When the bar closes, the value locks to the close. The historical line on the chart after the fact shows only the locked value, not the provisional values you watched.

Check. Inspect each slot's Power User block for the On Bar Close? setting.

Fix. If you did not want the repaint behavior, set the switch back to ON. If you did want the behavior, remind yourself that the historical shape of that slot line is the confirmed history; the live movement you watched is not stored.

9. Master smoothing is on and the pane feels slow

Likely cause. The master smoothing length is long enough to add meaningful lag on top of slot smoothing that was already in place.

Check. Note the master MA Length. Disable master smoothing temporarily. Compare how early the blend flips without the master pass.

Fix. Shorten the master length, switch to a faster master MA type, or turn master smoothing off and rely on slot slow lengths. There is no master smoothing setting that adds stability without lag.

10. Colors flip on almost every bar

Likely cause. Slow Length on one or more slots is too short for the kind of read you want. The default Slow Length is 3, which is reactive by design. In choppy tape, fast-vs-slow crosses can happen every few bars.

Check. Is the flipping happening on one slot only, on all slots, or on the blend?

Fix. Raise Slow Length on the affected slot. A Slow Length of 5 to 9 produces a much steadier regime read on most instruments at the cost of later flips. If the flipping is on the blend specifically, consider enabling a short master smoothing pass — but read scenario D in Workflows for the tradeoff.

11. Enabling a slot did nothing to the blend

Likely cause. The slot defaults to weight 0 on slots 4 through 10. Enabling a slot turns on its compute, plot, and alerts, but it does not set a weight. A weight-zero slot never steers the blend regardless of whether it is enabled.

Check. Open the slot's primary input block. Confirm Blended Weight is greater than zero. Also confirm that the other enabled slots still have the weights you remember setting — adding a new weighted slot reduces the share of the others.

Fix. Set a positive weight on the slot you want to contribute. If you wanted the slot to plot but not contribute — observer mode — leave the weight at zero and treat the slot as context rather than an input to the blend. Scenario B in Workflows walks the observer-slot pattern end to end.

When troubleshooting does not resolve it

If you have walked this page and the pane still behaves in a way you cannot reconcile, the next step is usually a configuration audit:

• Open the inputs dialog and write down, in order: which slots are enabled, their timeframes, their sources, their MA families, their lengths, their weights, their On Bar Close? posture.

• Compare against what you expected to see configured. The mismatch is usually small and easy to miss.

• If the configuration is as you intended and the behavior still looks wrong, the reading is more likely in Limitations & Trust Boundaries than a misconfiguration — in particular the alignment trap, cross-asset confusion, or sensitivity drift.

Where to go next

• The trust boundaries that cause most misreads: Limitations & Trust Boundaries.

• The working mental model the symptoms above assume: Visuals & Logic.

• Named setups you can return to when your own tuning has drifted: Workflows.