Troubleshooting

Troubleshooting

This page is organized by symptom. Find what you are seeing, then follow the diagnosis. Each entry helps you distinguish a setup error from a misunderstanding from a genuine product boundary.

The indicator shows an error message instead of drawing

Symptom: The pane displays a runtime error, typically mentioning a timeframe.

Likely cause: A slot's configured timeframe is lower than the chart timeframe. For example, slot 1 is set to 5m but the chart is on the 15m timeframe.

Fix: Either increase the offending slot's timeframe to be at or above the chart timeframe, or switch your chart to a lower timeframe. The error message should indicate which slot is the problem ("RSI 01 timeframe cannot be lower than the chart timeframe").

Why this happens: TradingView's multi-timeframe data request cannot reliably produce lower-timeframe data on a higher-timeframe chart. The indicator stops rather than drawing misleading data.

Lines are flat or missing at the beginning of the chart

Symptom: The first section of the chart history shows no oscillator lines, gaps, or flat lines stuck at zero.

Likely cause: Warmup. RSI needs RSI Length bars of data before it can produce a value. Then the RSI Smoothing MA needs its own lookback, and the Signal MA needs its own lookback on top of that. With On Bar Close enabled, one additional bar of offset is added.

How long it lasts: With default settings (RSI Length 14, RSI Smoothing 3, Signal Length 3, On Bar Close = true), expect approximately the first 20 bars of history to be blank. Higher-timeframe slots may take longer to populate because each HTF bar spans multiple chart bars, and the RSI calculation counts in HTF bars, not chart bars.

Fix: This is normal. Scroll forward past the warmup period. If you need earlier history coverage, consider shorter lookback settings — but that changes the oscillator's behavior, not just its warmup time.

I can only see the blended line — individual slot lines are invisible

Symptom: The blended RSI/Signal pair draws normally (green/red with fill), but no individual slot lines appear.

Likely cause: The "Hide RSI ## Plot" toggle is enabled for the affected slots. This hides the individual line but does not disable the slot — it still computes, contributes to the blend, and fires alerts.

Fix: Open the settings for each enabled slot and check the "Hide RSI ## Plot" toggle. Turn it off for the slots you want to see.

Alternative cause: If the slot is set to the chart timeframe and its RSI value is very close to the blended line, the individual line may be hidden behind the thicker blended line. Try increasing the individual slot's Line Width or temporarily disabling the blended plot to see if the slot line is there but visually obscured.

The blended line seems to track only one slot

Symptom: The blended RSI moves in near-lockstep with one specific slot, while other slots have different readings that do not seem to affect the blend.

Likely cause: Weight imbalance. One slot has a much higher weight than the others. Because weights auto-normalize, a slot at weight 100 with two other slots at weight 1 will dominate the blend — it contributes roughly 98% of the composite.

Fix: Check the weight settings for all enabled slots. If the imbalance is unintentional, adjust weights to reflect the relative importance you want each slot to have. If it is intentional, understand that the blend is essentially a lightly smoothed version of the dominant slot.

Alternative cause: If all weights are roughly equal but only two slots are enabled, and one slot has a na reading (from warmup or error), the blend defaults to the single valid slot. Check whether all enabled slots are producing values.

I set a slot's weight to zero but I am still getting alerts from it

Symptom: Alerts fire for a slot you thought you turned off by setting its Blended Weight to 0.

Cause: Weight = 0 removes the slot from the blended calculation, but the slot is still enabled. It still computes its RSI and Signal, still plots its line (unless hidden), and still fires all three of its alert conditions (Is Bullish, Is Bearish, Regime Flip).

Fix: If you want the slot fully silent — no computation, no plot, no alerts — use the "Enable RSI ##" toggle to disable it. Weight = 0 means "keep this slot active for monitoring but exclude it from the blend." It does not mean "turn it off."

Regime flips are happening very frequently — the slot line color is alternating every few bars

Symptom: A slot's line rapidly alternates between bright and dim, sometimes switching on consecutive bars.

Cause: The slot's RSI (K) and Signal (D) lines are very close together, causing them to cross and uncross frequently. This happens during periods of low directional conviction — momentum is near neutral and K oscillates around D.

This is not a malfunction. It is the oscillator accurately reporting that momentum is directionless in that slot's context. The rapid color changes are the visual equivalent of "I do not have a strong reading right now."

Fix: If the rapid flipping is producing too much noise for your workflow:

• Increase the slot's Signal Length by 1–2. A longer Signal is harder for K to cross, which reduces crossover frequency and focuses regime flips on more decisive momentum shifts. This trades sensitivity for stability — you will see fewer flips, but the ones you see will represent larger momentum changes.

• Recognize the rapid flipping as an ambiguous state and avoid acting on individual flips during this period. Wait for K to move decisively away from D before treating a regime flip as meaningful. If the slot line stays near zero and the colors keep changing, the most informative thing the oscillator is telling you is that momentum does not have a clear direction in that timeframe.

See the Visuals and Logic ambiguous churn scenario for more on reading this state.

The oscillator never seems to reach overbought or oversold

Symptom: The oscillator moves between approximately −50 and +50 in normal conditions, rarely if ever touching the ±70 default OB/OS lines.

Cause: The default OB/OS levels of ±70 correspond to standard RSI 85 and 15 — genuinely extreme values that most instruments reach only during strong, sustained momentum pushes. If you are expecting the same frequency of OB/OS touches you get from standard RSI at 70/30, those standard levels map to bipolar ±40, not ±70.

Fix: Decide what standard RSI threshold you consider overbought. Convert it using: bipolar = (standard RSI − 50) × 2. Set the oscillator's OB and OS levels accordingly. Common conversions:

The oscillator seems stuck near +100 or −100

Symptom: One or more slot lines are pressed against the ±100 boundary and are not responding to price changes.

Likely cause: The underlying RSI is at an extreme value (near 0 or 100 on the standard scale) and the bipolar rescaling compresses those extremes against the boundary. This happens during very strong one-directional moves where nearly all bars in the RSI lookback period are in the same direction.

Fix: This is the oscillator correctly showing that RSI is at an extreme. The compression near ±100 means the oscillator has less visual resolution at the extremes — a move from standard RSI 95 to 97 appears as a small shift from bipolar +90 to +94. This is a known characteristic of the bipolar scale, not a bug. The oscillator will unstick as the price move slows and the RSI begins to pull back from its extreme.

If this happens frequently on your instrument and timeframe, consider whether RSI is the right tool for those conditions. During strong one-directional moves, RSI naturally saturates. The oscillator is showing you that saturation honestly.

An alert fired but the chart does not seem to match

Symptom: You receive an alert notification (e.g., "Blended RSI Regime Flip") but when you look at the chart, the current state does not seem to match.

Likely causes:

1. The alert fired on the previous bar. Alerts fire at bar close. By the time you check the chart, the next bar may have already reversed the condition. This is especially common with regime flips near the K/D crossover — a one-bar flip that immediately reverts.

1. The alert is a state alert, not an edge alert. "Blended RSI Is Bullish" fires on every bar while the condition holds. If you set a "Once Per Bar Close" frequency, you will get a notification every single bar during a bullish regime. This is correct behavior — but it may feel like repeated false alerts if you expected a one-time notification.

1. A hidden slot changed the blend. If the blended regime flipped because a hidden (but enabled, weighted) slot's RSI shifted, the visible slot lines may not explain the blend's movement.

Fix: Check which bar the alert fired on (TradingView logs the bar time). Then work through each possibility:

• If the alert bar is one or more bars behind the current bar, the condition may have already changed. This is normal for edge alerts near K/D crossovers — the flip happened but did not hold.

• If you are getting repeated alerts on every bar, you are likely using a state alert ("Is Bullish" or "Is Bearish") with a frequency setting that fires on every bar close. Switch to the corresponding edge alert ("Regime Flip") if you only want the transition notification.

• If the alert is blended-level but the visible slot lines do not explain the blend's movement, check for hidden slots. A hidden slot with non-zero weight still drives the blend even though its line is not drawn.

See the Alerts page for the full state-vs-edge distinction and guidance on frequency settings.