Tradovate >= / <= Price Alerts Fire One Tick Late

You set an alert for exactly 5000.00 on the way up. Price prints 5000.00, sits there for a second, and your bell stays silent. Then a single tick at 5000.25 goes through and only now does the sound play. The alert didn't miss, and you didn't build it wrong. A greater-than-or-equal or less-than-or-equal alert on Tradovate can behave like a crossing rather than an exact touch, so it fires one tick past the value you typed instead of right at it. For a slow swing alert that's a rounding error. For a scalp entry or a tight breakout level, that one tick is the difference between being early and chasing. Here's what's happening under the hood and the one-tick trick that lands the alert exactly where you want it.

What's Actually Happening

Every Tradovate alert has three parts: a price level, a condition, and a notification type. When you drop an alert above the current price, the condition is “greater than or equal to” your value. Drop it below, and it's “less than or equal to.” The “or equal to” part is the whole point. You expect the alert to fire the moment price touches the number, not a tick later.

In practice, >= and <= alerts don't always honor the equal case. Price can print exactly at your value and the alert stays quiet. It only wakes up once a print lands one tick beyond the level, in the direction price was already moving. An upside alert at 5000.00 fires at 5000.25. A downside alert at 4980.00 fires at 4979.75. The condition ends up acting like a strict “greater than” or “less than,” even though the operator says “or equal to.” It's been seen on the desktop Trader app and on mobile web, and it's intermittent rather than constant, which is exactly what makes it easy to miss until it costs you an entry.

Why an “Or Equal To” Alert Skips the Equal

You don't need the internals to fix this, but knowing why it happens tells you when to expect it. A few things line up:

The alert watches the last traded price

A price alert generally evaluates against the last print that crossed the tape, not the resting bid or ask. If your level sits between trades, no print ever lands exactly on it. Say the last trade was 4999.75 and the next is 5000.25. The market clearly passed 5000.00, but nothing ever printed at 5000.00, so an equality check against the last price never sees a match until 5000.25 goes through. That alone produces a one-tick-late fire.

Quotes are sampled, not streamed tick-for-tick

The platform doesn't hand every micro-update to the alert engine instantly. Quote and DOM data refresh on a throttle, roughly on the order of once a second under load. If price kisses your exact level and moves on between two samples, the alert engine simply never sees the touch. It sees the “before” tick and the “after” tick, and the after tick is the one that fires the alert.

The comparison rounds toward a crossing

Put those together and the effective behavior is a crossing, not a touch. The alert reliably fires once price is unambiguously past the level, which is one tick beyond. That's dependable in its own way, it's just not what “or equal to” implies, and it's why compensating by exactly one tick works so cleanly.

The One-Tick Fix, Step by Step

Step 1: Know which side price is coming from

The direction of the nudge depends entirely on which way price is traveling into your level. An alert placed above current price is an upside (>=) alert; price rises into it and the late tick lands above your value. An alert placed below current price is a downside (<=) alert; price falls into it and the late tick lands below your value. Get this straight first, because nudging the wrong way makes the alert fire two ticks off instead of zero.

Step 2: Move the value one tick toward the price

Shift the alert value one tick onto the near side of your true level, so the platform's extra tick brings it back to the level you actually care about. The math is simple once you fix the direction:

Those examples use ES, where one tick is 0.25. On CL a tick is 0.01, on gold (GC) it's 0.10, on the Treasury contracts it's a fraction of a point. Always nudge by one tick of the specific contract, never by a flat 0.25 or a round handle. If you're unsure of an instrument's tick size, hover the DOM or check the contract spec before you set the number.

Step 3: Set the alert on the chart or DOM

Place the alert the way you normally would. On a chart, right-click the price level and choose the add-alert option, then set the condition and the nudged value. On the DOM, right-click the exact price cell and add the alert there. Either path lets you type the precise value, so enter the compensated number from Step 2 rather than the round level. Pick at least one notification you'll actually notice, sound and popup at minimum.

Step 4: Prove it with a throwaway alert

Don't trust the fix on the setup that matters. On a quiet, slow-moving contract, set a compensated alert a few ticks from the current price and watch precisely where it fires. If it now pings at your intended level instead of a tick past it, the compensation is working for that instrument and platform. If it still lands a tick off, double-check the direction of your nudge and the tick size. This one-minute test is worth far more than assuming.

Step 5: Manage and clean up alerts from the bell

Open the Alerts icon, the bell in the top-left of the workspace next to the New menu, to see every active, triggered, and expired alert in one place. This is where you edit a value if you nudged the wrong way, delete stale alerts that clutter the view, and confirm an alert is still armed rather than already spent. When an alert does fire, the browser plays a sound and the bell shows a red dot, so keep the panel handy while you verify the fix.

Step 6: Report the behavior to support

The nudge patches the symptom, not the cause. Email [email protected] with the details that make it reproducible: the exact instrument, the full condition and value, the platform you saw it on, and the plain fact that a >= or <= alert only fired one tick past the value. A specific report is the only thing that turns “some traders see this” into a tracked issue, and it's the fastest route to a definitive answer on whether it's expected or a defect.

Troubleshooting Table

When a One-Tick Alert Isn't Good Enough

Compensating by a tick is fine when the alert is just a nudge to look at the screen. But plenty of traders use a price alert as the trigger to act: hit the level, take the entry, arm the stop. The moment your reaction is the trade, a one-tick-late ping isn't cosmetic anymore. You either react a tick behind, or you pre-empt and hope. That's the gap worth closing with automation.

• Define the level where the logic is strong. A charting platform like TradingView lets you express the exact price condition, or a full strategy, and fire a webhook the instant it's met, with no dependence on a native alert that lands a tick late.
• Route it straight to Tradovate. PickMyTrade takes that webhook and acts on your account automatically, so the “alert” becomes an order at the level you set instead of a chime you still have to answer.
• Mirror across accounts. One trigger can drive several evaluation or funded accounts at once, so you're not manually re-arming a tick-sensitive alert on each screen.
• Rate-limit-safe routing. Order flow is spaced to stay inside Tradovate's request limits, avoiding the retry storms that cause their own lockouts.

Keep native alerts for eyes-on levels where a tick doesn't matter, and hand the price-precise triggers to a pipeline that fires on the number you actually chose.