Troubleshooting

Organized by what you are seeing on the chart, not by what the underlying cause might be. If something looks wrong, find the symptom below, work through the check, and fix the cause. If the symptom is not here and it is not covered in Limitations & Trust Boundaries, it is probably a TradingView-level issue (data feed, chart settings, alert wiring in the platform) rather than an indicator issue.

Each entry follows the same rhythm: the symptom, the most likely cause, a fast check, and the fix.

Symptom: The indicator refuses to run and shows a message about a slot timeframe

Message text, verbatim:

MACD 01 timeframe cannot be lower than the chart timeframe.

(The slot number in the message is whichever slot is misconfigured. If slots 03 and 07 are both below the chart timeframe, the script halts on the first one it checks.)

Cause. The indicator enforces that every enabled slot's timeframe is greater than or equal to the chart timeframe. Setting a slot below the chart timeframe has no honest reading — you cannot derive a 1-minute MACD after the fact from 5-minute bars.

Check. Look at the chart timeframe in TradingView's top-left. Open settings and inspect each enabled slot's Timeframe.

Fix. Either raise the offending slot's timeframe to match or exceed the chart, or drop the chart timeframe down. If you were deliberately asking for a lower-timeframe slot on a higher-timeframe chart, the indicator cannot provide that — use a separate chart at the lower timeframe instead.

Symptom: The indicator refuses to run and shows a message about Fast Length and Slow Length

Message text, verbatim:

MACD 01 Fast Length must be less than Slow Length.

Cause. A slot has Fast Length >= Slow Length. MACD by definition is the difference of a fast MA and a slow MA; setting them equal makes the MACD identically zero, and reversing them inverts the sign and invalidates the signal interpretation.

Check. Open settings. Inspect the named slot's Power User group for Fast Length and Slow Length.

Fix. Make Fast Length strictly less than Slow Length. Defaults are 12 and 26; any pair with fast < slow will clear the error.

Symptom: A slot line is pinned at 0 or 100 and will not move

Cause. Usually ATR collapse on the slot's context — the ATR denominator is small enough that even modest MACD values normalize to the sigmoid's asymptotes. Less commonly, ATR Sensitivity is set aggressively high and the current move is normal-sized.

Check. Identify which slot is pinned. Note the session — is this an overnight, holiday, or otherwise thin-liquidity period for the slot's symbol and timeframe? Look at the slot's ATR Length and ATR Sensitivity in the general Oscillator group. For cross-asset slots, check whether the cross-asset market is currently open.

Fix. If the cause is a thin session, there is nothing to fix — the reading is honestly reporting a small MACD against a small ATR, and it will un-pin when liquidity returns. If the cause is ATR Sensitivity, lower it back toward 1.0 and observe. If the cause is a cross-asset slot's market being closed, the slot will resume normal behavior when that market opens again.

Symptom: A slot line flickers color during the first few bars after load

Cause. Expected behavior during warmup. Each slot's color rule uses slot fast vs. slot slow when both are present, and falls back to slot fast vs. 50 during the brief window where the slot slow has not formed. That window ends the moment the signal line has enough bars to produce a value.

Check. Wait a few bars. If the flicker persists beyond the warmup period, reset the indicator by removing and re-adding it; if the flicker still persists, check whether Signal Length has been set to an unusually large value that delays signal formation.

Fix. Usually no action needed — give the slot its warmup. If the slot never stabilizes, inspect Signal Length in the slot's Power User group.

Symptom: A higher-timeframe slot's line is drifting during the chart bar

Cause. That slot has On Bar Close? set to OFF. The slot is reading the live, forming HTF bar, which revises with each chart close until the HTF bar itself closes. This is repaint, and it is what OFF does.

Check. Open settings. Inspect the drifting slot's On Bar Close?. Default for every slot is ON.

Fix. Flip On Bar Close? back to ON if you want stability. If you genuinely want the live HTF read, leave it OFF and treat the line's movement as honest intra-bar information that may not survive the bar. MTF & Repainting walks the tradeoff in detail.

Symptom: The All MACD Slots Bullish alert fires during weak conditions that do not look aligned

Cause. Usually slot correlation, not a bug. The alignment alert inspects every enabled slot whose values are present. If most enabled slots share source and lengths and only differ in timeframe, the alert fires whenever the underlying convergence story is persistent — even mildly. Alternatively, a weight-zero observer slot is participating in alignment and you have forgotten it is enabled.

Check. Open settings and list which slots are enabled. For each, note source, MA family, fast/slow/signal lengths. If the list reads "mostly the same ingredients at different timeframes," this is the alignment trap, not a malfunction. Also confirm that any observer slots you meant to park are either disabled or deliberately differentiated.

Fix. Either differentiate the enabled slots (different MA family, different sources, different length pairs, different tickers) or reframe how you interpret the alert — as information about correlation rather than independent agreement. Limitations & Trust Boundaries opens with this failure mode.

Symptom: An alert is firing on every bar

Cause. Expected for state alerts wired with "Once Per Bar Close." These are not transition alerts — MACD 01 Is Bullish fires every confirmed chart bar while slot 01 fast is above slot 01 slow.

Check. Open the alert in TradingView's alert dialog. Check the trigger mode.

Fix. If you want a one-shot notification after the alert is armed, set the trigger mode to "Only Once." If you want true transition behavior, the state alert alone will not give you that. This indicator does not plot per-slot slow lines, so TradingView cannot directly cross a plotted slot fast against that slot's internal slow line; use custom transition logic or another plotted MACD if your workflow requires literal per-slot crosses.

Symptom: A blend alert fires noticeably later than I expected

Cause. Master smoothing is enabled. The blend alerts read the smoothed blended fast and slow, which lag the unsmoothed values. This is structural, not a bug.

Check. Open settings, inspect the master smoothing group, note whether it is enabled and what MA/length is set.

Fix. If you want unsmoothed blend alerts, disable master smoothing. If you want both the smoothed visual and the unsmoothed alert behavior, the indicator does not offer that split — you would need to disable master smoothing and either accept the visual twitch or build a TradingView alert against an additional smoothing layer outside the indicator.

Symptom: A cross-asset slot's line is dragging the blend in a direction the chart instrument is not moving

Cause. Expected if the cross-asset slot is carrying meaningful blend weight and its symbol is diverging from the chart symbol. The blend is a weighted average and does not know about symbol identity; it mixes slot values regardless of which ticker each slot reads.

Check. Open settings, identify the slot with Optional Ticker set, note its weight. If weight > 0, the blend should be reflecting that slot's contribution.

Fix. Decide whether the cross-asset slot belongs in the blend at weight > 0 or whether you want it as context only. Observer mode (weight 0) keeps the line and its alerts active without pulling the blend. Workflows covers the cross-asset context scenario; Limitations & Trust Boundaries covers the dragging misread.

Symptom: The blend line disappears or reads na

Cause. Either every enabled slot has weight 0, or every enabled slot currently has na values (warmup, data gap, cross-asset market closed with no prior bars available, or a slot halted earlier in computation).

Check. Open settings. List enabled slots. Confirm at least one has weight > 0. If all weights look fine, the cause is most likely a temporary data condition on a cross-asset slot.

Fix. If no slot has weight > 0, raise at least one weight to a non-zero value. If the cause is a temporary data condition, wait for the relevant market to open or the data feed to resume.

Symptom: Changing ATR Length or ATR Sensitivity did not visibly change the pane

Cause. The changes apply per slot, but small changes on a quiet session may be visually imperceptible. Also, if the slot was already pinned at a boundary, small sensitivity changes may not un-pin it.

Check. Push the change harder — raise ATR Sensitivity from 1.0 to 3.0 temporarily and observe. Or drop ATR Length from 14 to 7.

Fix. Return to a value that gives you the resolution you want. There is no "correct" pair; there is only the pair that makes the pane readable for your instrument and session. Document the choice so you remember why you made it.

Symptom: Two slots that I configured identically show different colors or values

Cause. Either their timeframes differ (the most common case — the whole point of slots is that they run on independent timeframes), or their Optional Ticker fields differ, or one has On Bar Close? set differently, or their Power User MA-family parameters diverge.

Check. Compare the two slots input-by-input. Start with Timeframe, Optional Ticker, On Bar Close?, then the primary lengths, then MA family selections on both the MACD line and the signal, then the family-specific Power User parameters.

Fix. Align the inputs you actually want aligned. "Identical" in a workbench this configurable usually means "same except for one dimension I am varying on purpose." Name which dimension that is.

Where to go next

If the symptom looks like a genuine interpretation mistake rather than a configuration problem, read Limitations & Trust Boundaries — the alignment trap, ATR collapse pinning, and cross-asset misread all live there in full. If you are about to change inputs, Settings walks every control with the tradeoff attached. If the question is about the live HTF read vs. the confirmed one, MTF & Repainting is the page.