What Actually Stops Working When Your MT4 or MT5 Terminal Goes Offline

person
FXVPS
Share
What Actually Stops Working When Your MT4 or MT5 Terminal Goes Offline

“My positions are safe on the broker’s server, so it doesn’t matter if my computer turns off.” That sentence is half true, and the false half is where accounts get hurt.

Your positions do live on the broker’s server. So do some of the orders protecting them. But a surprising amount of what traders think of as “my stop” or “my risk management” is actually running inside the MetaTrader terminal on your machine — and when that terminal stops, those protections stop with it, silently, with no error on the broker’s side.

This guide draws the line precisely: what keeps working with the terminal off, what freezes, and how to audit your own setup so you know which category you are in before an outage tells you.

The Two Places an Order Can Live

Every protective instruction in MetaTrader lives in one of two places.

On the broker’s trade server. Once accepted, these are executed by the broker regardless of whether your terminal is running, connected, or even installed. Your computer could be switched off for a week and they would still trigger.

In your client terminal. These are instructions your terminal (or an EA running inside it) evaluates on every incoming price, and then sends to the broker as a modification or close request at the moment it decides to act. The broker knows nothing about them in advance. If the terminal is not running, nothing evaluates them and nothing is sent.

The difference is not visible on a chart. A trailing stop and a normal stop loss look almost identical in the trade window. That is the root of the misunderstanding.

What Keeps Working With the Terminal Off

These are server-side. They trigger whether or not your terminal exists:

  • Stop Loss attached to an open position
  • Take Profit attached to an open position
  • Pending orders — Buy Limit, Sell Limit, Buy Stop, Sell Stop, and on MT5, Buy Stop Limit and Sell Stop Limit
  • Pending order expiry, where you set one
  • The broker’s stop-out — margin call and stop-out levels are enforced by the broker, not by you

If you place a trade with a hard stop loss and take profit and then turn off your computer, both levels remain live on the server. This part of the common belief is correct.

📊 Key Stat: MetaQuotes’ own help documentation states that a Trailing Stop “works in the client terminal, not in the server (like Stop Loss or Take Profit)”, and that it “will not work, unlike the above orders, if the terminal is off.” Only the stop level the trailing stop last set remains in place.

What Stops Working With the Terminal Off

Trailing Stops

MetaTrader’s built-in trailing stop is client-side on both MT4 and MT5. The terminal watches price, and when profit reaches your trailing distance it sends a modification moving the stop loss. With the terminal off, the stop loss freezes wherever the trailing stop last put it. The MT5 help also notes that a trailing stop cannot act more than once every ten seconds for a given position, so even with the terminal running it is not tick-by-tick.

The practical consequence: a trade that ran 80 pips into profit with a 20-pip trail, while your terminal was running, has a stop locked in around 60 pips of profit. If the terminal then dies and price reverses, you keep that. But a trade that had only just started trailing when the terminal died is protected only by whatever stop was set at that instant — possibly your original stop loss.

Virtual (Stealth) Stops and Targets

Many EAs deliberately hide their stop and target from the broker. The EA holds the levels in memory and closes the position with a market order when price reaches them. The attraction is that the broker cannot see your levels. The cost is that there is no stop on the server at all. If the terminal stops, the position is completely unprotected until something closes it manually or the broker’s stop-out does.

⚠️ Warning: A position managed by an EA using virtual stops shows no stop loss in the trade window, which looks identical to a position where you simply forgot to set one. Check your EA’s settings for words like “stealth”, “hidden”, “virtual” or “invisible” stops. If present, a terminal outage leaves you with no protection whatsoever.

Break-Even Moves

“Move the stop to entry once price is 15 pips in profit” is EA logic. It runs on price updates in the terminal. Offline, it never fires, and the original stop stays in place.

Partial Closes and Scale-Outs

Closing half the position at the first target and letting the rest run is a sequence of market orders the EA sends when conditions are met. None of it happens with the terminal off.

Basket and Equity-Based Exits

Grid and martingale systems commonly close all positions when combined profit reaches a target, or when total drawdown hits a limit. That equity guard is often the only thing preventing a runaway basket. It is entirely client-side. Our grid and martingale EA requirements guide covers why these strategies are the least tolerant of downtime.

Time-Based Exits

“Close everything before the weekend” or “exit at 21:55 server time” only happens if the EA is running at 21:55. For why Friday exits matter, see our weekend gap and Sunday rollover guide.

Price Alerts and Notifications

Alerts set on MetaTrader charts, and push notifications triggered by your EA, are generated by the terminal. When the terminal is off, the alert you set to wake you up if price crosses a level never fires — which is exactly when you would have needed it.

Emulated OCO and Bracket Logic

MetaTrader has no native one-cancels-other link between two pending orders. EAs that emulate OCO (for example, a breakout straddle where filling one side cancels the other) need to be running to do the cancelling. Offline, both sides can be filled.

A Special Case: Prop Firm Rules

Prop firm daily loss and maximum drawdown limits are enforced by the firm’s own systems, not by your terminal. That means a terminal outage does not pause the rule. If an EA’s equity guard was what kept you inside the daily loss limit, and the terminal dies, the firm’s server will still breach the account when the limit is crossed. Our guide to prop firm rules and VPS compliance covers the rules that most often catch traders out.

Auditing Your Own Setup

Take fifteen minutes and go through each position-management behaviour your strategy relies on. For each one, answer a single question: if the terminal is off for six hours, does this still happen?

  1. Look at an open position in the Trade tab. Is there a value in the S/L column? If not, the position has no server-side stop.

  2. Read your EA’s input parameters. Look for trailing, break-even, partial close, basket, equity, virtual and time-exit settings. Every one of them is client-side.

  3. Check whether your EA sets a hard stop as a backstop. Well-designed EAs send a wide server-side stop loss as a disaster stop, then manage the real exit client-side. If yours does not, ask the developer whether it can.

  4. List your chart alerts. Anything you rely on to notify you is terminal-dependent.

  5. Write down the worst case. For each position type, what is the maximum loss if the terminal stops at the worst moment and stays down until you notice? If that number is uncomfortable, the fix is either a server-side backstop, or making sure the terminal does not go down.

💡 Tip: The simplest robust pattern is “hard stop on the server, clever management in the terminal.” Set a server-side stop loss at the level where you would accept the trade was wrong, and let trailing, break-even and partial logic operate inside that envelope. An outage then costs you optimisation, not the account.

Why This Is the Real Argument for a VPS

Most VPS marketing leans on milliseconds. For many traders, the stronger argument is this list. Every client-side protection above depends on a Windows machine staying powered on, connected and running MetaTrader continuously. A home PC fails that test regularly — sleep settings, updates, power cuts, Wi-Fi drops. A datacenter VPS is built to pass it.

It does not make client-side orders server-side. Nothing does, other than setting a real stop loss. What it does is drastically reduce how often the terminal is not there to run them. Pair it with automatic restart so a rare reboot does not become a long outage — our Task Scheduler restart guide shows how — and with alerts that tell you when something has stopped.

Best Practice: After any outage, before doing anything else, compare your open positions against the broker’s web or mobile platform and check each position’s S/L. Trailing and break-even levels that should have moved will not have. Adjust them manually, then restart the EA.

🚀 Keep your terminal running — FXVPS plans start at $29/mo with dedicated cores and datacenter uptime. Try it for 7 days for $2.99 via /try-risk-free/.

Summary

Stop losses, take profits, pending orders and the broker’s stop-out are server-side and survive anything that happens to your machine. Trailing stops, virtual stops, break-even moves, partial closes, basket and equity exits, time exits, chart alerts and emulated OCO all live in the terminal and stop the moment it does. Audit which of these your strategy depends on, add a server-side backstop where you can, and host the terminal somewhere that stays online.

Frequently Asked Questions

Does my stop loss still work if MT4 is closed?

Yes. A stop loss attached to a position is held on the broker’s server and triggers whether or not your terminal is running.

Does a trailing stop work if MT4 or MT5 is closed?

No. MetaTrader’s trailing stop runs in the client terminal. When the terminal is off, the stop loss stays at the last level the trailing stop set and does not move further.

Are pending orders safe if my computer turns off?

Yes. Limit, stop and (on MT5) stop-limit pending orders are stored on the broker’s server and will be filled when price reaches them, even if your terminal is off.

How can I tell if my EA uses virtual stops?

Open positions will show an empty S/L column in the Trade tab even though the EA is managing an exit. The EA’s inputs will usually include an option labelled stealth, hidden, virtual or invisible stops.

Does a VPS make trailing stops server-side?

No. It keeps the terminal that runs them online far more reliably than a home computer. The only truly server-side protection is a real stop loss or take profit.

Will a prop firm’s daily loss limit stop my trades if my EA is offline?

The firm’s system will breach the account when the limit is crossed, but it will not manage or close trades on your behalf in a way that keeps you inside the rule. Your own protections still need to be running.