A mental stop is an exit rule acted on manually, even when written in a plan. An accepted protective Stop Loss automates a specified trigger. That difference matters, but an ordinary stop does not guarantee its requested price or unconditional immediate execution.

Requested is not active

Our example: you request SL 95 to 97, but receive a rejection. The post-response reading still shows 95. A mental plan and current position parameters are different records.

Scroll sideways to see the full diagram

Requested is not activeA fictional long enters at 100 with active SL 95. A request for 97 is rejected; the post-response reading confirms 95. At PLN 2 per price unit, a fill at 95 would lose PLN 10 and a fill at 97 would lose PLN 6, assuming exact fills with no fees or slippage.Model price · long from 1001009795entry97: requested95: activeReply: rejectedAfter reply: still SL 95To 95: (100 − 95) × 2 = PLN 10To 97: (100 − 97) × 2 = PLN 6
Assumptions: Fictional long at 100; arbitrary price unit and linear result of PLN 2 per unit moved. The request to change SL 95 to 97 is REJECTED; the specified post-response reading confirms active SL 95. Loss amounts assume fills at those prices with no fees or slippage; they are not maximum losses. MQL5 documentation distinguishes a completed-request response from a rejected-request response. MT5 description places stop loss on the server; check actual conditions and execution for the instrument.
After changing your intention, check the response and current level rather than assuming activation.

Follow the difference: For the confirmed model level 95, (100 − 95) × 2 = PLN 10. Assuming “the stop is already at 97” would give (100 − 97) × 2 = PLN 6 and omit PLN 4. We do not invent a rejection cause or claim every rejection implies the same platform state: here 95 is independently specified and read.

A rule, request and accepted order are different records

A manual exit requires noticing the condition, sending an instruction and obtaining execution. Hesitation, connectivity or platform availability can interfere. Experience does not remove gaps or technical delays. A chart line or phone alert is not confirmation of a protective order.

For an accepted server instruction, you need not click close at the triggering moment. Still check its active parameters, trigger convention and execution conditions. In MT5, Stop Loss runs on the server; the documentation also describes a failed triggered operation being attempted again on a later eligible tick. Triggering and completed closure are not interchangeable confirmations.

Different mechanisms · check the actual product
Manual ruleRequires a person and an executable closing instruction.
Ordinary stopAutomates the trigger; actual execution may differ from the specified level.
Stop-limit, where availableA limit constrains price but can leave the order unfilled.
Guaranteed stop, where availableA separate provider service with eligibility, fees and contractual scope.

IG’s UK order guidance distinguishes normal stops, with potential slippage, from a guaranteed-stop option. Do not assign that option to every instrument, broker or account. SEC guidance describes stop-limit nonexecution for US stock orders; it does not establish identical position-closing features across CFD products.

Calculate losses at the assumed actual fills

Our hypothetical EUR/USD buy fills at 1.0900. Assume a USD account, 100,000 EUR per lot, volume 0.10 lot and a pip of 0.0001. That is 10,000 EUR and USD 1 per pip. A requested stop at 1.0850 is 50 pips away, corresponding to a USD 50 price loss if filled exactly there.

Alternative assigned exit fills · extra costs excluded
Fill at 1.085050 pips; USD 50 price loss
Fill at 1.083070 pips; USD 70 price loss
Fill at 1.0760140 pips; USD 140 price loss; 2.8 times USD 50

These are arithmetic alternatives, not observed relative stop performance. Either manual delay or automatic execution conditions can produce an overrun, among other causes. The prices are actual-fill assumptions, not mid-spread quotes. An ordinary stop-level calculation is not a certain maximum loss.

Changing a stop or quantity changes exposure. Assess both the rule and resulting account risk before a modification. The desire not to book a loss is not an analytical justification; related decision questions appear in revenge trading.

Check what remains active when the terminal closes

MT5 built-in trailing runs in the terminal. When it stops, it cannot send further modifications; the last successfully set server Stop Loss can remain active. Check that a server level was actually set, rather than assuming the trailing menu selection created it immediately.

A virtual stop implemented by an EA or script is a separate arrangement. Identify the operating instance, connection and failure procedure. A VPS label alone does not show that the intended programme is running or that the local and remote instances have the same state.

In the diagram’s fictional model, a long enters at 100 with active SL 95. The change request to 97 is rejected, and a separate subsequent reading confirms 95. At PLN 2 per arbitrary price unit, an exact fill at 95 would lose PLN 10; at 97, PLN 6. Assuming 97 active would omit PLN 4 under the model. No rejection cause is supplied.

A response and current state must both be checked. The model does not claim every rejection leaves the same state on every platform. A reliable check belongs in a system of trading discipline, rather than a multi-year experience test that guarantees manual execution.

A wick or Bid-only chart does not explain the trigger

For the ordinary Forex rule described in MT5, long-position SL is checked against Bid and short-position SL against Ask. Exchange instruments can follow different trigger conventions. Identify the relevant quote, time and product before interpreting a chart.

Our hypothetical short has SL 1.1030. Bid remains 1.1022. In state A, Ask 1.1024 gives a two-pip spread and is below the SL. In B, Ask 1.1032 gives ten pips of spread and is two pips above the SL, although Bid is still eight below it. A Bid-only manual alert and the specified server rule can therefore react differently.

Meeting the trigger does not determine the fill or demonstrate manipulation. Preserve both quotes, timestamps, order IDs and execution history. A later price reversal alone is not evidence of a targeted stop hunt or grounds for assuming a manually timed “genuine break” will avoid loss.

Re-read active parameters after any modification or position change. An ordinary stop can be changed or cancelled and therefore does not automatically enforce discipline throughout a trade.

Before leaving a position unattended

Confirm the order, quantity, trigger, relevant trading hours and response to a failure. Include plausible worse-fill scenarios and additional costs in the exposure review. If you cannot assess or supervise the arrangement, consider reducing exposure, closing or declining a new position rather than relying on an unverified line.

Review changes against explicit earlier rules. A trailing adjustment is not a guarantee of banked profit; tightening or widening needs its actual consequence assessed. No rule here establishes a universally best stop for every retail account.

Related reading: trading discipline as a system — checks, confirmations and critical breaches; accepting losses — separate the closed result from a recovery goal; revenge trading — inspect a proposed next decision independently of the previous loss.