Most traders who enter NQ automation think their problem is the signal. It's almost never the signal.

The actual failure modes are execution-layer problems that no TradingView backtest will ever surface. Here's what we learned:

---

1. Duplicate contract spam on fast candles

When your webhook fires inside an active bar and price re-triggers your condition, most alert systems send multiple order payloads in the same tick. NinjaTrader receives two contracts. You're 2x exposed with zero awareness it happened.

Fix: an intrabar firewall built into the script. One signal per candle. Zero exceptions. Resets at bar close — not on price action.

2. Static levels in an adaptive market

Backtests with fixed take-profit and stop distances look clean in low-vol and catastrophic in expansion. The NQ's 5-minute ATR swings from 4 points at 9:35am to 18+ by 10:45am in active sessions. Fixed levels can't handle this.

Fix: adaptive volatility envelopes that recalculate on every bar close. When NQ expands, your levels expand. Risk stays proportional.

3. Entering reversals inside CHOP

Firing reversal signals while the market is consolidating with no directional bias is a random number generator. No edge. Just friction.

Fix: a CHOP index trend gate that reads current market structure before confirming any entry. No directional intent = no trade.

---

These three things — intrabar firewall, adaptive envelopes, CHOP gating — were the entire gap between a system that performs and one that blows accounts.

Build your execution stack first. The signal follows.