Known issue in PineForge Codegen 1.9.1: state in per-bar timeframe requests #314

State inside request.security can produce incorrect results when the requested timeframe is chosen per bar, even when both choices are multiples of the chart and feed timeframe.

On BTCUSDT with a 1-hour chart and feed, the following script chooses 120 or 180 minutes. In released 1.9.1, its entry quantities matched TradingView for 126 of 205 entries. In the 120-minute arm, 17 of 96 matched. These are exact joins by entry time.

//@version=6
strategy("Selected timeframe", currency = currency.NONE, initial_capital = 1000000)
// state inside a request whose timeframe (120 or 180 minutes) is chosen each bar
payload() =>
    var float saved_v = na
    saved_v := nz(saved_v) + close
    saved_v
tf_v = close > open ? "120" : "180"
got_v = request.security(syminfo.tickerid, tf_v, payload())
qty_v = 1 + int(got_v / 1000) % 5
if bar_index > 6 and bar_index % 7 == 3
    strategy.entry("L", strategy.long, qty = qty_v)
if bar_index > 6 and bar_index % 7 == 5
    strategy.close("L")

Workaround: not yet verified.

Fixed in the next release (1.10.0). The measured fix candidate matches all 205 entry quantities for this case. No release date is announced here.

Updated 2026-11-03: this issue first said "the next patch release". The next release is 1.10.0, a minor release.

See also: pineforge-4pass/pineforge-engine#718.