Reading 'invalid stops' errors without losing your mind
Posted: Wed Oct 28, 2026 4:04 am
Few messages are as irritating as "invalid stops". The platform rejects an order, and the reason isn't obvious. In most cases, one of a handful of causes is responsible.
The stop or target is too close to the current price, violating the broker's minimum stop level. The direction is wrong: a buy's stop must sit below the price, and a sell's above. The price used for calculation is stale, so by the time the order arrives, the market has moved and the stop is now inside the minimum distance. The digits are wrong, with the stop price containing more decimals than the symbol allows. Or the stop level changes dynamically, widening around news.
A systematic check helps: read the symbol's stop level, compare it with the distance in the order, and confirm that prices are normalized to the right number of digits. For buys, remember that stops compare against the bid, and for sells against the ask.
Automated systems should fetch fresh prices right before sending, and log the full request on failure.
A little diagnostic table speeds up the hunt. Column one lists the symbol's stop level in points. Column two lists the distance between the order price and the current price. Column three shows whether the stop is on the correct side. Column four shows the number of digits. Filling it in for a failed order usually pinpoints the culprit in under a minute.
What's been the most common cause of invalid stops, and how was it fixed?
The stop or target is too close to the current price, violating the broker's minimum stop level. The direction is wrong: a buy's stop must sit below the price, and a sell's above. The price used for calculation is stale, so by the time the order arrives, the market has moved and the stop is now inside the minimum distance. The digits are wrong, with the stop price containing more decimals than the symbol allows. Or the stop level changes dynamically, widening around news.
A systematic check helps: read the symbol's stop level, compare it with the distance in the order, and confirm that prices are normalized to the right number of digits. For buys, remember that stops compare against the bid, and for sells against the ask.
Automated systems should fetch fresh prices right before sending, and log the full request on failure.
A little diagnostic table speeds up the hunt. Column one lists the symbol's stop level in points. Column two lists the distance between the order price and the current price. Column three shows whether the stop is on the correct side. Column four shows the number of digits. Filling it in for a failed order usually pinpoints the culprit in under a minute.
What's been the most common cause of invalid stops, and how was it fixed?