summary: report-specific session behavior — timezone selection, TradingView indicator matching, weekday filtering, managing custom sessions, and common session mistakes on reports.

every report on edgeful has a session dropdown — and changing it changes everything about what the report measures. the reference close shifts, the high/low levels change, and the results can look completely different.

this article covers the report-specific details: timezone selection, TradingView indicator matching, weekday filtering, managing custom sessions, and common mistakes. for the foundational overview of sessions — what each session is, the reference close, day rollover rules, and how to pick the right session — see sessions overview.

reports are where the timezone feature has the most impact. when you select a session on a report page, the timezone determines exactly which price candles fall inside that window — and that changes every calculation.

the built-in London session now runs 8:00 AM to 4:00 PM in Europe/London time (UTC+1), matching the London Stock Exchange hours. the built-in Asian session uses its local timezone as well. if you've been using the platform for a while and your London or Asian data looks slightly different, that's why — the session boundaries shifted to their local timezones instead of Eastern.

the NY and Daily sessions haven't changed. NY is still 9:30 AM to 4:00 PM ET. Daily is still 6:00 PM to 5:00 PM ET.

when you create a custom session, you now pick a timezone along with your start and end times. the timezone you choose is the timezone those times are in — so "7:00 AM to 3:00 PM" means something different depending on whether you've selected America/New York or Europe/London. make sure you're picking the timezone that matches how you think about your trading day.

for the full breakdown of the timezone update — including how to revert to the old Eastern-based sessions — see time zones on edgeful in the sessions overview.

some reports let you filter by specific weekdays. this is useful if you want to study day-of-week patterns — for example, whether Monday gaps behave differently than mid-week gaps, or whether Friday ORBs have a different profile.

the rollover rule matters here. since the "day" is defined by the session rollover — not the calendar — a trade at 7 PM ET on Thursday shows up under Friday's data. so when you filter for "Friday" in a report, you're getting everything from Thursday's rollover through Friday's rollover.

a few ways to use weekday filtering:

the session concept carries over to edgeful's TradingView indicators too. many indicators have a "by session" version — and the distinction matters.

for example:

same concept applies to previous day's range vs. previous day's range by session, pivot points vs. pivot points by session, and fibonacci vs. fibonacci by session.

if you're trading futures and your TradingView indicator levels don't match what you see on edgeful, this is almost always why — you're using the standard version of the indicator instead of the "by session" version. switch to the session variant and the levels will line up.

with the timezone update, there's one more thing to get right: the timezone in your TradingView indicator needs to match the timezone of the session you've selected in edgeful.

if your edgeful session is set to Europe/London with an 8:00 AM to 4:00 PM window, your TradingView indicator's session time and timezone also need to be Europe/London, 8:00 AM to 4:00 PM. if one is in London time and the other is in Eastern, the reference levels won't line up — and that'll look like the data is wrong when it's actually just a timezone mismatch.

the same applies to the IB indicator. if you're running the IB report on the London session, your TradingView IB indicator needs to use the same session start time in London time (8:00 AM) so the first-hour range plots correctly on your chart.

the market sessions indicator is especially useful here. it draws boxes on your chart showing exactly where each session falls — so you can visually confirm that your indicator levels and your edgeful report are referencing the same candles.

if you've created a custom session you no longer need, you can remove it directly from the reports section.

that's it — the session is deleted and won't appear in your session dropdown anymore.

note: this only removes custom sessions you've created. the 4 built-in sessions (NY, London, Asian, Daily) can't be deleted.

using different sessions across reports. if your gap fill report is set to NY but your IB report is set to London, your levels won't align. keep all your core reports on the same session unless you have a specific reason to mix them.

mismatched timezones between edgeful and TradingView. this is the most common issue since the timezone update. if your edgeful session uses Europe/London time but your TradingView indicator is set to America/New York, the plotted levels won't match. always check that both are using the same timezone and session times.

forgetting to check the session on TradingView. the indicators on your chart and the reports on edgeful need to be using the same session. if one is set to "by session" and the other isn't, the levels won't match.

ignoring the rollover when filtering by weekday. if you're filtering for a specific day but your trades happen after the rollover time, they'll show up under the next day. always account for the 6 PM ET (futures/stocks) or 5 PM ET (forex/crypto) rollover when reading weekday-filtered data.

using 60-minute candles to capture the NY open. 60-minute candles start and end on the hourly mark — so the first 60-minute candle starts at 10:00 AM, not 9:30 AM. you can't measure 9:30–10:30 AM with a 60-minute candle. if you want to capture the first 30 minutes of the NY session open, use a 30-minute candle instead.