A Trailing Stop Can Freeze When MT5 Is Offline

On MetaTrader 5, a locally managed trailing stop stops updating when the terminal is offline. The last Stop Loss accepted by the server can remain active, but the terminal cannot calculate and send a tighter level while it is disconnected.

This difference matters after a volatile policy week. A USD/JPY position may move quickly following the BOJs hike to 1.25%, then reverse when traders reassess the vote split and guidance. A trader who sees a profitable position on a phone may assume a desktop trailing rule has kept moving. That assumption is unsafe unless the platform or provider confirms server-side operation.

What remains active after disconnection

Feature	Terminal online	Terminal offline
Existing Stop Loss	Active	Last accepted level remains
Trail calculation	Updates with quotes	Stops locally
New modification	Can be sent	Cannot be generated by the terminal
Floating P/L	Changes with price	Continues to change

MetaTraders documentation explains that a trailing stop runs in the client terminal and that only one trailing rule can be set per open position. It also explains that the stop moves in the profitable direction and does not loosen automatically.

The operational audit is straightforward. Open the platform journal and find the latest successful Stop Loss modification. That server-accepted value is the protection that existed at the time of disconnection. A level the trailing algorithm would have calculated later is not an order.

Power settings, laptop sleep, internet interruptions and platform restarts all belong in risk management. A virtual private server may help keep the terminal running, but it creates a new dependency that must be monitored. Some brokers provide separate server-side trailing features, and their rules should not be assumed to match MT5.

This 2026 MT5 trailing-stop guide shows the interface and setup. The MetaTrader manual remains the authority for the terminal behavior.

The workflow closes with evidence. Test a small demo position, allow the trail to move, disconnect the terminal and inspect the server-side stop from another device. That test answers the operational question more reliably than the label “trailing stop.”