summary: running ORB across NY, London, and Asian sessions on a single ticker is 3 separate chart tabs, 3 separate alerts, and session-specific filter tuning — here's the full walkthrough, and the gotchas that trip people up on the first go.

you can run the ORB algo on more than one session at a time. the edge is real — NY, London, and Asian ORBs each capture different market dynamics, and most futures traders only have one of them working for them.

the setup itself is mechanical once you've done it once. the part that trips people up is assuming you can stack all 3 sessions on a single chart. you can't — each session needs its own chart tab, its own indicator instance, and its own alert.

this article walks you through the whole thing from scratch.

make sure you've got the basics in place first. if any of these aren't done yet, start with setting up TradingView for edgeful algos.

if you're running the 3 sessions on different broker accounts (e.g., a personal account and a prop firm account), you'll need a separate strategy per account. see running multiple algos — rules and conflicts.

here's the piece most people miss on their first attempt — you cannot put 3 ORB indicators on a single chart, one configured for each session. TradingView alerts lock to the indicator instance and the chart symbol at the time of creation. if you try to layer NY, London, and Asian on one chart, the alerts collide and you'll get duplicated or missed fills.

the clean setup: one chart tab per session, one ORB indicator per tab, one alert per tab. 3 tabs total.

they can all be on the same ticker (e.g., MES) — the separation is just at the chart tab level.

do this 3 times — once for NY, once for London, once for Asian. the steps are identical for each session.

in TradingView, click the plus icon at the bottom of the screen to open a new tab. load your futures symbol (e.g., MESH2026 for March Micro E-mini S&P). use the specific front-month contract, not the continuous symbol (MES1!) — continuous is for backtesting only, except for Topstep accounts.

for the full reference on continuous vs. front-month and handling rollovers, see futures contract rollovers.

[SCREENSHOT NEEDED: TradingView with 3 chart tabs labeled NY, London, Asian at the bottom]

open the indicators panel → invite-only scripts → add the ORB algo indicator to the chart.

open the indicator settings (double-click the indicator name on the chart) and set the session dropdown to the session this chart tab is for. on your NY tab, select NY. on your London tab, select London. on your Asian tab, select Asian.

this is the single most important setting on this page — it tells the algo when to calculate the opening range and when to allow entries.

for the full breakdown of what each session actually covers (especially after the recent timezone update), see choosing a session for your trading hours.

this is where most people lose 2 out of 3 sessions — they copy the filter min/max values from NY and reuse them on London and Asian. those values don't transfer.

ORB sizes are structurally different across sessions. on NQ for example, London ORBs tend to run smaller than NY ORBs — so a 0.50–1.00 NY filter goes silent on London because almost no London ORBs fall in that range.

for each session, pull up the ORB by-levels report on edgeful for that ticker + session combination and rebuild your filter range against that distribution. the full procedure (with the inclusive-min / exclusive-max gotcha) is in no trade visualized on your chart — specifically the re-tune filters when you change sessions section.

right-click the indicator on the chart → Add alert. in the alert dialog:

for the full alert setup detail, see setting up TradingView alerts for algo automation.

this takes 5 seconds and saves you an hour every time something goes wrong. name your 3 alerts with the session baked in:

when the TradingView alert log fires — or doesn't — the session is the first thing you need to identify. generic names like "ORB alert" or "MES alert" force you to open each alert and check its settings to figure out which session it belongs to. don't do that to yourself.

for how to read the alert log, see reading the TradingView alert log.

go back to step 1 and do it 2 more times. when you're done, you should have:

before you walk away, confirm each session can actually fire. the easiest way is to wait for a session to go live and watch the alert log.

do this for each of the 3 sessions over the course of their active hours. if one session fires and another doesn't, the issue is almost always either filter tuning (the range is silently excluding every ORB on that session) or an alert that got left in a stale state after you changed a setting.

you changed a setting and the alert stopped firing. TradingView alerts lock to indicator settings at the moment of creation. any change — session, filter range, risk parameters — requires deleting the alert and recreating it.

the London or Asian session never fires. 9 times out of 10 this is filter tuning. the ORB by-levels report for that specific session will show you the actual distribution — tune against that, not against your NY range.

you see IB levels but no ORB levels on one session. check the session dropdown — it's easy to accidentally leave it on the default when you duplicate a chart. open the indicator settings and confirm each tab is set to its intended session.

the contract rolled and now none of your alerts fire. all 3 alerts are tied to the same expiring contract symbol. you have to delete and recreate all 3 on the new front month. see contract rollover: why your algo silently stopped trading.