A trailing stop moves a position’s Stop Loss as the market moves favourably. It starts acting when the position reaches the configured profit-distance threshold. It does not loosen the Stop Loss when the market moves against the position.

The trailing calculation runs in the desktop terminal, rather than continuously on the trading server. The terminal must be running and connected for it to keep updating the Stop Loss.

For a hypothetical Buy position opened at 100, imagine a trailing distance of 2 price units. At a price of 102, the trailing calculation can first request a Stop Loss at 100. If price rises to 103, it can request 101. If price then falls to 102.5, it does not move that Stop Loss backwards to 100.5. The examples assume requests are accepted; they do not promise execution at those prices.

For a hypothetical Sell position opened at 100, the same distance starts acting after price falls to 98, requesting a Stop Loss at 100. A further fall to 97 can move it to 99. A subsequent rise does not make the stop less restrictive. These are illustrative price distances, not recommended settings or values to enter for a particular instrument.

The terminal’s distance is expressed in points. A point is the instrument’s price increment; it is not automatically a pip or an amount of money. Decimal precision and contract settings matter. Before choosing a distance, check the exact instrument’s specification and the position’s actual Stop Loss.

A manually placed Stop Loss and a trailing setting are different. A trailing setting may not yet have placed any stop because its activation threshold has not been reached. Do not treat the setting alone as proof that a server-side Stop Loss exists. After an update, verify the actual stop level rather than assuming the request was accepted.

If the terminal or connection stops, the last successfully placed server-side stop remains, but the price can move without further trailing adjustments. When you reconnect, review the position and its current stop. Neither a VPS nor continuous connectivity makes stop execution or a maximum loss guaranteed.

Closing the terminal, losing its connection or shutting down the computer stops further trailing updates. The last Stop Loss successfully placed remains on the server. If no Stop Loss was placed yet, a trailing-stop setting alone does not provide one.