TradingView has increased the number of separate external data requests a Pine Screener script can use from five to 40. The change, announced on 23 October, brings the screening tool’s request ceiling into line with the standard limit available in its charting environment. It addresses a practical problem for traders and research desks whose indicators ran on individual charts but failed when applied across many symbols in a scan.[1]
A Pine Script request can obtain another symbol, a different timeframe, an index reading or financial data. A script combining a weekly trend, a daily momentum measure and shorter-interval volume may need several such calls. With the previous five-request restriction, a user often had to remove cross-market comparisons or construct a simplified version for the screener.[1]
The 40-call ceiling is not the same as permission to import 40 independent feeds without further restrictions. TradingView says it counts separate request calls; requests with identical arguments can be counted once, while calls made within imported library functions count against the same limit. Users must review the combined script rather than only the visible code in the main indicator.[1][2]
Richer screening has not removed every technical constraint
Pine Screener specification after the October update
| Control | Company documentation |
|---|---|
| Separate request.*() calls per script | 40, previously 5 |
| Eligible minute intervals | 1, 5, 15 and 30 |
| Eligible hourly intervals | 1, 2 and 4 |
| Longer intervals | Daily, weekly and monthly |
| Maximum indicator calculation history | Last 500 bars |
| Concurrent scans | One at a time |
| Index source size | Up to 4,000 symbols |
The company’s documentation retains an approved set of screener timeframes: one, five, 15 and 30 minutes; one, two and four hours; and daily, weekly and monthly intervals. A request for an unsupported custom interval will not become valid simply because the higher call ceiling has spare capacity.[1]
Other operational limits also remain. TradingView says the screener can process a chosen index with up to 4,000 symbols, calculates on the last 500 bars, and permits only one scan at a time; a separate browser tab cannot run another concurrent scan while one is active. Certain script inputs are unsupported or fall back to their defaults, so identical-looking chart and screen configurations may still behave differently.[1]
For brokerage-facing analytics, the improvement may reduce duplicated scripting work when integrating multi-timeframe screeners into analyst workflows. It does not change venue market hours, execution permissions, data-source commercial terms or the need to examine whether a displayed quote is delayed.[1][2]
TradingView’s announcement gives practical examples of comparing shares with an index benchmark and including more timeframes in the same screen. It provides no independent before-and-after latency benchmark, fill-quality evidence or promise that complex scans finish faster. The verified change is capacity for additional data requests inside the screener, not automatic investment performance.[1]
Sources & further reading
- Pine Screener now supports up to 40 request calls per script TradingView · 23 Oct 2026 · Accessed 31 Oct 2026
- TradingView Pine Screener: key features and requirements TradingView Help Center · 23 Oct 2026 · Accessed 31 Oct 2026