Evaluate history-dependent functions on every calculation, then apply the condition to their result. Calling `ta.sma()` only when `close > open` builds an inconsistent internal history because skipped bars are missing from that call’s series. Moving the call to global scope gives it consecutive bar data. The conditional `plot()` then controls display without changing when the moving average is calculated.
This link opens the Pine Script AI Coding Agent overview. It does not run or change code on this page.
Before and after
Both artifacts include the version declaration and the code needed to inspect the stated problem. The diff lists the lines that change between them.
//@version=6
indicator("Conditional calculation demo")
float average = na
if close > open
average := ta.sma(close, 20)
plot(average)//@version=6
indicator("Conditional calculation demo")
float average = ta.sma(close, 20)
plot(close > open ? average : na)--- broken.pine
+++ fixed.pine
@@
-float average = na
-if close > open
- average := ta.sma(close, 20)
-plot(average)
+float average = ta.sma(close, 20)
+plot(close > open ? average : na)Continue with a guide that shares the same scope, type, history, or resource mechanism.
Compilation error
Runtime error
Open the Coding Agent overview to paste editable Pine Script, explain the intended behavior, and request a review. Compile and test the result in TradingView before using it.
Paste your code to fix this error