Pine Screener Update: Index Scans, More Scripts, and Why a Screen Is Not an Alert

TradingView announced on 1 September 2026 that its Pine Screener can scan the constituents of an index directly and lets you pick a script from the full Indicators dialog instead of only your Favorites. You no longer need to build a watchlist and favourite a script before you can test an idea across a large universe of symbols.

The practical consequence is faster research, not automation. A screen shows which symbols match your script's conditions when you run it. It does not create an alert, send a webhook or place an order. This article explains what changed, which scripts the screener can use, why a screen can disagree with your chart, and what has to happen before a screened idea can reach MetaTrader through PineConnector.

What changed

TradingView announced the update on 1 September 2026 (the post was updated on 17 September 2026)^[1]. Before it, a Pine Screener scan needed two preparation steps: a watchlist built by hand, and the script added to Favorites. The Pine Script release notes for August 2026 record the same change^[2]. What is different now:

• Symbol source. Before: watchlists only. Now: a watchlist or an index, one at a time. TradingView says the two are mutually exclusive and multi-select is not supported yet^[1].
• Choosing a script. Before: Favorites only. Now: the full Indicators dialog, with Personal (Favorites, My scripts, Invite-only, Purchased), Built-in (Technicals) and Community (Editors' picks, Top, Trending, Store) sections. A script no longer has to be a favourite first.
• Interval and inputs. Before: inside the script settings. Now: separate controls in the toolbar.
• Compatibility. Before: you found out when a scan failed. Now: scripts known to be unsupported appear greyed out, with a tooltip.
• Switching source. Changing the source clears the previous results but keeps your script, interval and inputs, so you rescan rather than start again^[1].

Index scans run against the index's constituents, which can be a large universe of symbols. If the size of a universe matters for your plan, check the screener's current limits in TradingView's Help Center^[3].

Which scripts the screener can use

A greyed-out script is not the only kind that fails. The announcement explains that TradingView can only flag scripts whose incompatibility is known in advance, meaning scripts that are not indicators or have no plots. Every other script can be selected, but some may still fail to run^[1]. The Help Center lists the requirements in full^[3]. Use them as a checklist before you rely on a screen:

• An indicator with output. The script must produce at least one supported plot (plot(), plotbar(), plotcandle(), plotchar(), plotshape(), plotarrow() or hline()) or an alertcondition(). Profiles, strategies, patterns and the Financials category are not supported.
• One indicator per screen. Filters come from that indicator's plots and alert conditions; table columns come from its plots only.
• Supported timeframes only. 1, 5, 15 and 30 minutes; 1, 2 and 4 hours; 1 day, 1 week and 1 month. Custom timeframes are not supported, and any timeframe a script requests must be on the same list.
• Five data requests at most. No more than five separate request.*() calls in the scanned script.
• Some inputs are ignored. input.timeframe(), input.symbol() and input.time() are not supported; the screener uses the script's default values instead.
• A shorter history. The indicator calculates on only the last 500 bars.
• Pine version. Custom alert conditions are not compatible with scripts written in Pine v3 or earlier.

Why a screen can disagree with your chart

Several of those requirements mean the screener may not calculate exactly what your chart shows. Each rule below comes with the check to make when a result looks wrong. The effects follow from TradingView's stated requirements; we have not measured them on particular scripts.

• Only the last 500 bars. A calculation that needs a long history or a long warm-up can produce a different value. Compare one symbol's plotted value on the chart with the screener's column.
• Timeframe, symbol and time inputs ignored. A setting you changed on the chart through input.timeframe(), input.symbol() or input.time() is replaced by the script's default. Read the script's defaults for those inputs.
• Supported timeframes only. A script built around a custom interval cannot be screened on it. Check the interval shown in the screener toolbar.
• Selectable is not the same as compatible. A script can be chosen and still fail to run. Check that the scan completes and the columns contain values.
• Results belong to the scan. Changing the source, inputs, timeframe or filters needs a rescan before the results mean anything.

As an illustration: you screen an index on the 1-day interval with a script that has an input for a higher timeframe, which you set to 1 week on your chart. The screener ignores your chart setting and calculates with the script's default for that input. If the default is different, the two results are not comparable, even though the script and symbol are the same.

Screening, alerting and execution are separate steps

A screen tells you about the moment you scanned. To act on a condition later, you need an alert that keeps evaluating it, and only an alert can send a webhook. That leaves two practical routes from a screen to an automated workflow:

• An alert per symbol for the few candidates you care about, created on the chart with the same script and inputs.
• A watchlist alert on a list that holds the candidates, where your TradingView plan includes watchlist alerts (TradingView's pricing page listed them from the Premium plan when checked on 23 September 2026)^[4]. One alert then covers every symbol on the list, and TradingView adds or drops symbols as the list changes^[5]. Multi-condition alerts cannot be used for watchlist alerts^[6], so a screen that combined several filters needs that logic inside one script condition before it can drive a watchlist alert.

For either route to reach PineConnector, the alert's message has to be a valid instruction for the exact broker symbol. PineConnector's guidance is to use {{ticker}} only when TradingView's ticker matches your broker's symbol^[7]. An index scan often produces stock symbols whose names at an MT5 broker carry a prefix or suffix, so check each one. Symbol Mapping in PineConnector can translate names, and it is included with the PineConnector Plus and Pro plans^[8]. The watchlist alerts guide covers what TradingView documents about {{ticker}}, what it leaves undocumented for watchlist alerts, and the symbol checks in more detail.

Limitations and common mistakes

• Treating a result as a signal. A symbol in the results table has not triggered anything. Nothing is sent to PineConnector from the screener.
• Assuming a selectable script works. Only scripts that are incompatible in a detectable way are greyed out. Check that the scan completes and the columns hold values.
• Comparing different calculations. Ignored inputs and the 500-bar history can make the screener's value differ from the chart's. Compare on one symbol before trusting a whole list.
• Screening with a strategy. Strategies are not supported. If your idea lives in a strategy, you need an indicator version of the condition to screen it.
• Stopping at the screen. A candidate list is research. The alert, the message and the demo test are still separate steps.

What to check before acting on a screen

1. Confirm the script is an indicator with a supported plot or alertcondition(), uses supported timeframes and at most five request.*() calls.
2. Check the script's defaults for any timeframe, symbol or time inputs, since the screener uses them.
3. Spot-check one result against the chart on the same interval.
4. Decide how you will be notified going forward: alerts per symbol, or a watchlist alert where your plan allows it.
5. If the alert will send an instruction to PineConnector, confirm the script actually offers a usable alert, using the checks in TradingView alert syntax for automation, and that every symbol matches your broker.
6. Run PineConnector's demo test workflow and compare the Alerts log, the Bridge and the broker account^[9]. At the broker, an accepted order, a filled deal and an open position are separate checks.

TradingView also added an AI Screener to its Stock Screener on 17 August 2026, which builds filters from a sentence^[10]. The AI Screener is a separate tool from the Pine Screener, and the same rule applies: a screen finds candidates and sends nothing.

Reviewed 23 September 2026. Facts were checked against the linked sources on that date. No screen or alert described here was run; the example is illustrative.

Related reading

• TradingView updates for alert-based automation: a practical index
• How to use watchlist alerts in TradingView
• TradingView alert syntax: format messages for automation
• Convert a Pine Script indicator into an automated strategy
• Pine Script alert() function: automate strategy signals

Sources

1. TradingView Blog – Pine Screener: scan any index, pick any script, published 1 September 2026, updated 17 September 2026, accessed 23 September 2026.
2. TradingView – Pine Script release notes, August 2026: Pine Screener improvements, accessed 23 September 2026.
3. TradingView Help Center – TradingView Pine Screener: key features and requirements, accessed 23 September 2026.
4. TradingView – Pricing and plan comparison, accessed 23 September 2026.
5. TradingView Help Center – Watchlist alerts: your trading edge, accessed 23 September 2026.
6. TradingView Blog – Introducing multi-condition alerts, published 23 October 2025, updated 24 October 2025, accessed 23 September 2026.
7. PineConnector Docs – Connect your strategy, accessed 23 September 2026.
8. PineConnector Docs – Match your broker's symbols, accessed 23 September 2026.
9. PineConnector Docs – Test your setup, accessed 23 September 2026.
10. TradingView Blog – AI Screener: transform your ideas into ready-made screens, published 17 August 2026, updated 21 August 2026, accessed 23 September 2026.

PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.