MT5 invalid stops error

Causes, most likely first

1. The stop is closer to price than the broker's minimum distance

Every broker enforces a stop level — a minimum distance between current price and any stop or target. On XAUUSD this is frequently wide enough to reject stops that your strategy considers perfectly reasonable. Check it in Market Watch: right-click the symbol, open Specification, and read "Stops level". If your calculated stop is smaller, the order will be rejected every time.

2. The stop is on the wrong side of the market

A buy needs its stop below and its target above; a sell is the reverse. This sounds obvious and is a genuinely common bug in hand-configured setups, particularly when a distance is entered as a negative number.

3. The price is not aligned to the tick size

Stop prices must be a whole multiple of the symbol's tick size and rounded to its digit count. A calculated stop of 2401.23456 on a two-decimal gold symbol is invalid. Round to the symbol's digits before sending.

4. The broker rejects SL and TP attached to the initial order

Many ECN brokers, including Exness, will not accept an order that arrives with protection attached — the position must be opened first and modified afterwards. Our engine handles this by sending orders with zero SL and TP and attaching protection immediately after the fill. If that modification fails, it force-closes the position rather than leaving it unprotected. See SL and TP not set.

Why this happens

This one error message covers at least four unrelated problems, which is why it is so frequently misdiagnosed. MetaTrader does not tell you which constraint you violated, only that you violated one.

The stop level is the cause that breaks automated systems most often, and it is invisible until it bites. A strategy developed against a broker with a zero stop level will fail on every order at a broker requiring $2.00 of distance on gold, and nothing about the strategy is wrong.

The stop level can also change with conditions. Some brokers widen it during news, so an EA that has been running cleanly starts rejecting orders for a few minutes each week. If your rejections cluster around scheduled releases, that is what is happening.