summary: you can run as many algos as you want, on as many tickers as you want, at the same time — there's no limit on the number of active strategies. but there are rules about what can run on the same chart, the same account, and the same ticker. break those rules and you'll get overlapping alerts, duplicate orders, or missed trades. this article covers all of it.
the core rule: one algo variant per chart
don't run multiple algo variants on the same TradingView chart. alerts will overlap and create conflicts.
what counts as a "variant"? each algo has different versions:
algo | variants |
ORB | standard, 2TP, breakeven stop |
IB | standard, breakeven stop |
gap fill | single variant |
engulfing | standard, 2TP |
running ORB standard and ORB 2TP on the same chart = conflict. running ORB standard and IB standard on the same chart = also a conflict. each algo indicator needs its own chart tab.
running ORB on one chart tab and gap fill on a different chart tab — that's fine. for the full variant breakdown, see algos — overview.
same ticker, different algos — use separate accounts
don't run two algos on the same ticker in the same broker account. if ORB and IB are both trading NQ into the same account, their entries and exits collide — edgeful only tracks the position each algo opened, so one algo's exit can close or net against the other algo's position, leaving you with conflicting or orphaned orders.
the rule: only one algo per ticker per account at a time. if you want to run two different algos on the same ticker, send each one to a different account — a separate broker account, eval, or funded account.
example: you want to run ORB and IB on NQ.
create an ORB strategy pointed at account A → build its alert on an NQ chart tab
create an IB strategy pointed at account B → build its alert on a separate NQ chart tab
each alert points to its own strategy's webhook URL, and each account only ever holds one NQ position at a time
the one exception — non-overlapping sessions. two algos on the same ticker in the same account is safe if their sessions never overlap. every algo flattens its position at the end of its session (an end-of-session close-out), so if algo A's session fully ends before algo B's session begins — e.g. ORB on a 09:30–11:00 session and IB on a 13:00–16:00 session — the two are never holding a position at the same time and there's nothing to conflict. the requirement is strict: if the sessions touch or overlap at all, you're back to conflicting orders. if you're not certain the sessions are fully separate, use separate accounts.
running two different algos on different tickers in the same account is fine (e.g. ORB on ES and gap fill on NQ) — the conflict only happens when two algos share the same ticker in the same account during overlapping sessions. full alert setup walkthrough: setting up TradingView alerts for algo automation.
same algo, different tickers
this is the most straightforward setup. one strategy at edgeful can handle multiple tickers — as long as they're all going to the same broker account.
example: you want to run ORB on ES, NQ, and YM.
create one ORB strategy in the algo dashboard → get your webhook URL
create 3 separate TradingView alerts — one for each ticker — all pointing to the same webhook URL
edgeful routes each trade to the correct contract at your broker
one strategy, one webhook, 3 alerts. clean and simple. because each alert is a different ticker, there's no position conflict — the one-algo-per-ticker-per-account rule is still satisfied.
the one thing to watch is exposure and margin. running the same algo across several tickers in one account means several positions can be open at the same time — so your total market exposure and margin requirement stack up. make sure the account has enough margin to hold every position the algo could open simultaneously, and that the combined exposure fits your risk plan and any prop firm drawdown limits.
same algo, different accounts
if you're running the same algo on multiple broker accounts — say a personal account and a prop firm account — each account needs its own strategy.
example: ORB on your Tradovate live account and your ProjectX eval account.
create strategy #1 in the dashboard → select Tradovate live → get webhook URL #1
create strategy #2 in the dashboard → select ProjectX eval → get webhook URL #2
on TradingView, create 2 alerts for the same indicator/chart — each with its own webhook URL
each account is completely independent. a failed trade on one doesn't affect the other. for the full list of supported brokers, see which broker accounts work with edgeful algo automation?
the multi-account lead/follower setup
if you're running 10, 20, or 40+ prop firm accounts, creating individual strategies and alerts for each one isn't practical.
the better approach: use a lead account model.
create one strategy in edgeful pointed at your lead account (a single Tradovate or NinjaTrader account)
set up one TradingView alert with that webhook
use a third-party trade copier to copy trades from your lead account to all follower accounts
the flow: TradingView alert fires → webhook goes to edgeful → edgeful executes on lead account → trade copier replicates to all follower accounts.
this way you only need 1 webhook per strategy — not 40. your trade copier handles the distribution. for the full prop firm playbook — which copiers work, how to configure them, and what to watch for — see using edgeful algos with prop firms and multiple accounts.
day-of-week conflicts
every algo has day-of-week settings — you can enable or disable longs and shorts for each day. this is useful, but it can also create unexpected behavior if you're not paying attention.
example: you have gap fill set to trade gap ups on Monday. but your personal rule is no trading on Mondays. if you forget to disable Monday in the algo settings, it'll fire anyway.
the fix: before going live, review the day-of-week toggles in your TradingView indicator settings for every active algo. make sure they match your actual trading plan.
and remember — if you change any day-of-week settings, you need to delete and recreate the TradingView alert. alerts lock in settings at creation time. full handoff: applying algo settings changes — what to do after you optimize and make algo setting changes.
max loss interactions
most algos have both a max loss per day setting and a max loss per trade setting.
when the daily max loss is hit, all open positions close immediately — regardless of where your TP or SL levels are. this is a safety net, not a target.
one important exception: the IB algo does not have a max loss setting. it relies on stop-loss placement and position size for risk management.
if you're running multiple algos on the same broker account, their max-loss-per-trade settings operate independently. algo A hitting its daily max loss doesn't disable algo B. but if both algos are trading the same account, you could end up with a combined loss that exceeds what either algo would allow individually.
something to think about when planning your multi-algo setup — especially for prop firm accounts with strict drawdown rules. for the mechanics of how max-loss and stop-loss interact during a live session, see customizable algo parameters and risk controls.
a practical checklist
before going live with multiple algos, run through this:
each algo indicator is on its own TradingView chart tab (no stacking)
no two algos are trading the same ticker on the same account at the same time — split them across separate accounts, or make sure their sessions never overlap (each algo closes out at the end of its session)
each broker account has its own strategy in the edgeful dashboard
each TradingView alert points to the correct webhook URL
day-of-week settings match your trading plan for every algo
max loss per day settings account for your broker's drawdown limits
total exposure and margin across all open positions fit your account size and any prop firm limits
if using a lead/follower model, the trade copier is configured and tested
you've paper traded each strategy individually before combining them