Position opened with no stop loss or take profit

Causes, most likely first

1. The broker requires protection to be attached after the fill

Exness and many other ECN brokers reject orders carrying SL and TP, so a correctly written EA opens the position bare and modifies it a moment later. If you catch the terminal between those two steps you will see an unprotected position that is protected a second later. This is normal.

2. The modification failed and was not retried

If the follow-up modification is rejected — usually by the stop level — a poorly written EA will leave the position open and unprotected indefinitely. This is the dangerous case. Our engine force-closes the position instead, on the reasoning that an unintended flat position is recoverable and an unmonitored leveraged one is not.

3. The EA is designed to manage exits in code rather than with orders

Some systems deliberately hold no server-side stop and close positions from their own logic. This works only while the terminal is running — a disconnect, a crash or a power cut leaves the position with no protection whatsoever. Ask any vendor directly whether their exits are server-side.

Why this happens

A server-side stop is honoured by the broker whether or not your machine is on. A stop held in EA logic is honoured only while MetaTrader is running, connected and responsive. That difference does not matter until the one day it matters enormously.

The Exness requirement to attach protection after the fill is a genuine constraint rather than a design choice, and every EA running on such an account has to deal with it. What separates implementations is what they do when the second step fails.

If you are evaluating a bot, this is a good specific question to ask: what happens if the SL modification is rejected. The answer tells you a great deal about how carefully the failure paths were considered.