summary: if your algo indicator isn't plotting entry, TP, and SL levels on your chart, the algo couldn't find a valid trade with your current settings — here's how to diagnose and fix it.
what this means
if no trade is displayed on your TradingView chart, the algo was unable to determine a valid trade using the settings you've selected. the conditions for the strategy weren't met during that session.
this isn't a bug — it's the algo doing its job. it only triggers when all of your configured conditions line up.
review your algo settings
the most common cause is a setting that's too restrictive for the current market conditions. open the indicator settings on your TradingView chart and check these:
ORB algos:
max ORB size — if you've set this to 0.50 but the actual opening range was 0.64, no trade triggers. use TradingView's measure tool to check the actual range size for that session, then adjust accordingly.
min ORB size — if the opening range is smaller than your minimum, the setup doesn't qualify. lower the threshold or focus on instruments that consistently produce ranges that meet your criteria.
timeframe — make sure your chart timeframe matches what the indicator expects. most ORB indicators are designed for specific timeframes.
IB algos:
IB range size — same concept as ORB. if the initial balance range is outside your configured min/max, no trade fires.
extension targets — if your TP is set to an extension level that rarely gets reached for your instrument, you may see fewer setups. check the IB by-levels report for historical fill rates.
all algos:
session — confirm you're looking at the right session. if your algo is configured for the NY session but you're checking the chart during London hours, there won't be a setup.
trading hours — if you've restricted the algo to specific hours, setups outside that window won't display.
how size thresholds work — inclusive mins, exclusive maxes
this is a common gotcha that causes missed trades. edgeful's ORB and IB size boundaries use inclusive minimums and exclusive maximums:
minimum — inclusive. an ORB/IB size that equals the minimum is included. range 0.00–0.50 includes 0.00.
maximum — exclusive. an ORB/IB size that equals the maximum is excluded. range 0.00–0.50 excludes 0.50.
so a range of 0.00–0.50 covers 0.00 through 0.49, but not 0.50 itself.
setting up non-overlapping ranges
if you're running multiple configurations with different size ranges, set them up so the max of one range becomes the min of the next:
small: 0.00–0.50 (includes 0.00 through 0.49)
medium: 0.50–1.00 (includes 0.50 through 0.99)
large: 1.00–2.00 (includes 1.00 through 1.99)
no overlap, no gaps. an ORB/IB of exactly 0.50 goes into "medium," not "small."
common boundary mistakes
setting 0.00–0.49 and 0.50–1.00: unnecessary — just use 0.00–0.50 and 0.50–1.00. the exclusive max handles the boundary for you.
forgetting the max is exclusive: if your max ORB/IB size is 0.55, trades of exactly 0.55 won't match. increase to 0.56 if you want to include 0.55.
re-tune filters when you change sessions
this is the single most common reason an algo that ran fine in NY goes silent when you switch it to London or Asian.
ORB and IB size distributions are structurally different across sessions. the NY open produces bigger ranges than the London open on most futures — and the Asian session is different again. a filter tuned for one session won't translate to another without re-calibration.
example: an ORB filter of 0.50–1.00 on NQ might cover most NY sessions cleanly. copy the same algo to the London session and you may see no trades for weeks — because London ORBs on NQ tend to be meaningfully smaller, and most of them fall below your 0.50 minimum.
the algo isn't broken. the filter is wrong for the session.
when you change the session on an algo, re-tune the filter:
open the ORB by-levels or IB by-levels report in edgeful for your ticker + the new session
check the historical size distribution — what ranges does that session actually produce?
set your min/max to capture the band you want to trade
don't copy NY settings over blindly. each session needs its own calibration.
if you trade the same instrument across multiple sessions, you'll end up with 2 or 3 versions of the same algo — one per session, each with its own filter. that's expected.
verify the actual range on your chart
use TradingView's measure tool to manually check the opening range or initial balance for that session. compare the high-to-low distance against your configured thresholds.
if the actual range is consistently above or below your settings, adjust the thresholds to match what your instrument typically produces. you can use the ORB or IB by-levels report in edgeful to see the historical distribution of range sizes for your instrument and session.
after adjusting ranges, manually verify a few trades — e.g., an ORB of 0.75 should match range 0.50–1.00, not 0.00–0.50.
check your chart type
make sure you're using regular candlesticks — not heikin ashi. heikin ashi candles average price data, which creates mismatches with the algo's price levels. this can prevent the algo from detecting valid setups and will cause order rejections if a trade does fire.
if you've been using heikin ashi, switch to regular candlesticks and check if the setup now appears.
confirm you're on the right contract
make sure your chart is loaded with the correct contract for your instrument. for live trading, use the current front-month contract (e.g., NQM2026) — not the continuous contract (NQ1!).
if you recently switched contracts after a rollover and the indicator isn't plotting, remove the indicator from the chart and re-add it on the new contract.
sometimes there's just no setup
not every session produces a valid trade. if the market opens flat, trades sideways through the range, or the range is abnormally large or small — the algo correctly stays out. that's the filter working as designed.
if you're seeing this frequently, consider whether your settings are too restrictive for your instrument's typical behavior. use the strategy tester to backtest with adjusted settings and find a balance that captures enough setups without being too loose.
still stuck?
if you've checked all of the above and still can't figure out why the algo isn't plotting, reach out via the in-app chat in edgeful. include a screenshot of your TradingView chart showing the session in question and your indicator settings — the team can take a look.