Repository navigation
Known issue in PineForge Engine 1.9.1: non-multiple requested timeframes #718
Description
Values may differ from TradingView when a requested timeframe is not a multiple of the feed timeframe. In the measured case, a fixed, state-free request.security call for 75 minutes consumes a 60-minute feed and gives different entry quantities without a warning.
On BTCUSDT with a 1-hour chart and feed, the following script produced 205 entries. Their quantities matched TradingView for 74 entries and differed for 131; entry times were joined exactly. This reproduces on released 1.9.1.
//@version=6
strategy("Selected timeframe", currency = currency.NONE, initial_capital = 1000000)
// a fixed 75-minute request on a 1-hour chart
got_v = request.security(syminfo.tickerid, "75", close)
qty_v = 1 + int(got_v) % 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.
A named runtime warning in the report is planned first. A fix is in progress. No release date is announced here.
Edited 2026-11-03: the earlier note named a fix approach that has not been confirmed.
Activity
Follow a request's timeframe on every bar, and keep persistent state …
luisleo526 commentedon Nov 7, 2026
Status: the fix is in review and planned for the 1.11.0 release. This issue stays open until the fix is on main; we will close it then with the commit that fixes it.
luisleo526 commentedon Nov 9, 2026
Status at v1.11.0: the requested-bar session-grid part has been in place since v1.10.0 (#727). The original case (a 75-minute request on a 60-minute chart: the caller, the quantity and the warning) is not fully fixed in v1.11.0; the per-site warning it needs is planned for the next minor release. This issue stays open.
Engine train 1: CI rounds under 15 minutes, and five fixes (#850)
luisleo526 commentedon Nov 13, 2026
Status 2026-11-13: the per-site warning for a requested timeframe that is not a multiple of the feed timeframe is merged on main today and ships in 1.13.0 (planned 2026-11-15). We confirm by 2026-11-14 whether that completes the 75-minute case in this issue, and close it or give the date for what remains.
🤖 Generated with Claude Code