TradingView Pine Screener: 40 request.*() Calls, the Plan, the Fixes

TradingView's Pine Screener now lets a script make up to 40 request.*() calls, the same limit as the chart. Until TradingView's update of October 23, 2026 it allowed 5, so many multi-timeframe indicators had to be cut down before they'd scan. Identical calls with the same arguments count once; calls inside an imported library count too. The Pine Screener itself needs a Premium or Ultimate plan, per TradingView's pricing page on 2026-10-29.

The counter above reads your script the way TradingView describes the count. Below: what changed, what counts, how to run a scan, and the errors that keep a script out of the screener whatever its count.

What changed on October 23, 2026?

The limit went from 5 request.*() calls per script to 40. TradingView's post, Pine Screener now supports up to 40 request calls per script, dated October 23, 2026: "Until now, there was a catch: a script could make no more than 5 request.() calls in the screener, while the same script on Supercharts could make up to 40." And: "Pine Screener now supports up to 40 request.() calls per script — the same limit as the chart."

What that opens up, in the post's words:

• Scan across timeframes. "Combine conditions from different intervals in one script – say, a weekly uptrend, a daily RSI reading, and a 4-hour volume spike — and filter for symbols that pass all of them."
• Compare against a benchmark. "Pull in an index or another symbol and use it in your conditions — for example, to find stocks outperforming the S&P 500 over the last month."
• Run heavier indicators as they are. Dashboards, scripts that check several lookbacks, and indicators built from libraries that make their own requests: "the ones you previously had to simplify or keep a separate 'screener version' for".

Our example in the counter does the first two in one script. It makes eight unique calls: over the old limit, well inside the new one.

The Pine Screener help now says the same: "No more than forty separate request.*() calls can be used inside of the scanned script." On the chart, TradingView's Pine limits page gives 40 unique calls, "or up to 64 unique calls if the user has the Ultimate plan". The screener's help says forty and doesn't mention Ultimate's 64; we couldn't test whether an Ultimate account gets more in the screener, so keep a script for the screener at 40 or fewer.

What counts as a request.*() call?

Every unique call to a function in the request.*() namespace. "Every time a script asks for data it doesn't already have — a value from another timeframe, another symbol, an index, financials — that is one request.*() call," TradingView's post says. The Pine limits page lists the functions that count: request.security(), request.security_lower_tf(), request.currency_rate(), request.dividends(), request.splits(), request.earnings(), request.quandl(), request.financial(), request.economic() and request.seed().

Four rules decide the count, from TradingView's pages:

1. Identical calls count once. "Identical calls with the same arguments count as one." The limits page shows a loop calling request.security(syminfo.tickerid, "1D", close) 50 times without an error, because each call is the same.
2. Different arguments count separately. The same page changes the timeframe on each pass of that loop, and the script "will reach the request.*() call limit while executing the loop and raise a runtime error". By the same rule, we read a function called with three timeframes as three calls, and so does the counter.
3. Library calls count. "Calls inside imported library functions count toward the limit," even, the limits page adds, "if the script already calls the same request.*() function with the same arguments in its main scope". The counter can't see inside a library: open its source and add its calls.
4. Tuples share a call. One request.security() that returns [close, high, volume] is one call. All of a script's requests together can return at most 127 tuple elements, per the limits page.

request.footprint() has its own rule: one unique call per script, and only Premium and Ultimate users can run scripts that call it.

How do you cut a script's request.*() count?

Merge calls that ask the same symbol and timeframe, and drop the repeats. The counter lists both under "How to cut the count", and the film's "Cut the count" tab shows the merge happen. Before:

//@version=6
indicator("Three calls")
c = request.security(syminfo.tickerid, "240", close)
v = request.security(syminfo.tickerid, "240", volume)
a = request.security(syminfo.tickerid, "240", ta.sma(volume, 20))
plot(v > 2 * a ? c : na)

After, one call:

//@version=6
indicator("One call")
[c, v, a] = request.security(syminfo.tickerid, "240", [close, volume, ta.sma(volume, 20)])
plot(v > 2 * a ? c : na)

Three calls on the same symbol and timeframe become one, and the script returns the same values. Two more ways:

• Compute on the chart's own timeframe where you can. A value on the screener's own interval needs no request at all.
• Keep loops from changing arguments. A loop that requests a new symbol or timeframe on every pass makes one call per pass. If you need ten symbols, that's ten calls, and the counter says so.

If you trimmed a script to fit the old limit of 5, TradingView's own suggestion is to undo it: "If you cut requests from a script to fit the old limit, now is a good time to put them back."

How do you run a script in the Pine Screener?

Add the indicator to your favorites, open the Pine Screener, pick a source and the indicator, set filters, then Scan. TradingView's post: "Nothing changes in how you work: add the indicator to your favorites on the chart, select it in Pine Screener, set your filters, and run the scan." The steps, from the Pine Screener help:

1. Add the script to your favorites on the chart. The screener's Add indicator dialog lists the scripts saved there: your own, built-ins and community scripts.
2. Open the Pine Screener. From TradingView's home page, Products → Screeners → Pine, or go to tradingview.com/pine-screener/.
3. Pick the source: one of your watchlists, or an index. An index can hold up to 4,000 symbols. One source at a time.
4. Click Add indicator and choose the script. One indicator per screen. Its first ten plots become filters and table columns, and two of its alert conditions are added.
5. Set your filters on its plots or alert conditions, then click Scan. Change the source, the inputs, the timeframe or the filters and you scan again.

We're on the free Basic plan, so these steps are TradingView's, not ours. Signed out on 2026-10-29, the Pine Screener's page showed a BETA label and "Log in to use Pine Screener" over a Log in button.

Why won't my script run in the Pine Screener?

Six causes, each from the Pine Screener's help or TradingView's post, and the fix for each. The counter flags all six, and a note's "Show line" button selects the line to fix in your pasted script.

Two limits that aren't errors but change results: the screener "calculates data based on only the last 500 bars on the chart", and it doesn't support Indicator-on-Indicator or custom timeframes. Everything else about the Pine Screener "remains the same", TradingView's post says.

Which TradingView plan has the Pine Screener?

Premium and Ultimate. On TradingView's pricing page, read on 2026-10-29, the Screeners section ticks Pine Screener for Premium and Ultimate and crosses it out for Basic, Essential and Plus. Prices per month, billed annually, the same day:

The stock, ETF, DEX and crypto screeners are on every plan, Basic included; the Bond Screener is Ultimate only. If the Pine Screener is the only reason you'd pay, run the counter first; if you're choosing a plan for several features, the plan picker ticks them all at once.

Where we stand

On 2026-10-29 we read TradingView's October 23, 2026 post, its Pine Screener help, its Pine limits page and its pricing page, and opened the Pine Screener signed out. We're on the free Basic plan and haven't run a scan: the scan steps are TradingView's own. The counter is ours: it reads your source in your browser, counts calls by the rules above and sends nothing anywhere.

We write Pine indicators ourselves: each tool in our Pine v6 stack is a .pine file you paste into the Pine Editor. TradingView doesn't endorse us. We're in its partner program, so our links to TradingView are partner links: if you open a new account through one and buy a plan, TradingView may pay us, at no cost to you.

Use this animation on your site.Embed this animation