you pull up a report on edgeful, then check the same thing on TradingView — and the levels don't line up. the previous day high sits in a different spot, the daily open is off, the numbers just don't agree.

nine times out of ten it isn't a bug. it's the 6:00 PM ET rollover — the moment futures start a new trading day. edgeful is built around that boundary. if your TradingView chart is drawing the day on a different boundary, the two will disagree in a specific, predictable way. here's the whole picture.

stocks are simple — they trade 9:30 AM to 4:00 PM ET, so a "day" is just a calendar day. futures aren't like that. CME futures (NQ, ES, GC, CL, and the rest) trade nearly around the clock, and a new trading day starts at 6:00 PM ET the evening before — when the Globex session reopens — running through 5:00 PM ET the next day.

so the futures "Tuesday" actually begins Monday at 6:00 PM ET. that's the boundary edgeful anchors its futures data to — the same one the exchange uses to settle the day.

TradingView can draw its daily candle on a different boundary depending on your chart's timezone and session settings. when it does, the daily open, high, low, and close it shows you are measuring a different window than edgeful — and the levels won't match.

this is where it bites most. on edgeful, PDH means previous session high — the high of the prior completed session, where the session rolled at the 6:00 PM ET boundary (or at your selected session's close). it does not mean the high of the previous calendar day.

on a "by session" report — the variants futures, forex, and crypto traders should be using — "previous day" is the prior NY, London, or Asian session, not midnight to midnight. the previous day high you see is built on that session window.

if your TradingView indicator is set to a calendar-day boundary while your report is on a by-session variant, the previous-day levels land in different places. they're measuring different days.

the Asian session confuses people the most, because it runs overnight relative to New York. Tokyo's hours fall in the ET evening and early morning — so the session crosses midnight ET.

that means a single Asian session can straddle two calendar dates. edgeful labels it by the trading day it belongs to, anchored to the 6:00 PM ET rollover — so what edgeful files under a given day's Asian session may have started the evening before in ET. match it on TradingView with a calendar-day mindset and the date looks off by one.

when you recreate an overnight session as a custom session, the overnight toggle has to be on — that's what tells the session it crosses midnight. set the same timezone and the same start / end on both your report and your TradingView indicator, or the boxes drift hours apart.

a few reports — opening candle continuation, ORB, IB — are built around the opening candle, the first candle of the session. on the NY session that's the candle that opens at 9:30 AM ET. not 9:15, not 9:00.

the windows measured from there:

one gotcha: don't try to capture the 9:30 open with a 60-minute candle. a 60-minute candle starts on the hour, so its first bar runs 10:00 - 11:00 and skips the open entirely. use a 30-minute candle to catch the first 30 minutes cleanly, or a 15-minute candle for the ORB window.

timezone and session explain almost every mismatch. two other causes are worth knowing:

both are covered in more depth in why do my report numbers look different from edgeful videos?.

when edgeful and TradingView disagree, check these in order — it's almost always one of them:

for the exact timezone and session-window values to enter on each indicator, see setting TradingView session times to match your edgeful reports.