Your Trading Robot Stopped Trading: Causes and How to Know Immediately
A silent robot can be more difficult to notice than a losing trade. Positions remain open, a grid stops being managed, and signals are missed while you assume the terminal is working. Here are common reasons an MT4/MT5 robot stops trading and how connection monitoring can reveal a terminal outage.
Why a trading robot goes quiet
- The VPS restarted or failed. A Windows update or hosting incident stopped the machine, and the terminal did not restart.
- MetaTrader froze or closed. A crash, memory problem, or accidental closure interrupted it.
- The broker connection was lost. “No connection” means quotes and trading requests cannot flow normally.
- Automated trading was disabled. The AutoTrading or Algo Trading setting may have been changed or reset.
- The account was logged out. Changed credentials or a lost session disconnected the terminal.
- The robot itself failed. An error can stop its logic even while the terminal remains open.
Why an interruption matters
Without open positions, downtime may mean missed entries. With open exposure, especially a grid or martingale, it can leave positions without the management the strategy expects. Broker-held stop-loss and take-profit orders are distinct from actions that require a running robot. Know which protections remain active without the terminal.
Detecting missing data
Connection monitoring watches for an absence of updates. If the account has sent no data for a defined period, a server can raise an alert even though no trade event has occurred. This differs from trade notifications, which need a trade to trigger them.
A heartbeat proves that the data channel is active. It does not prove that AutoTrading is enabled or that another robot's internal logic is healthy. Investigate those separately when data still arrives but expected trades do not occur.
How FilMonitor checks the connection
The FilMonitor Collector sends account snapshots every 20–60 seconds. If updates stop, the server detects the gap and can send an offline alert to Telegram and your phone. The default offline rule applies after about 20 minutes without data. Receipt still depends on the server, network, and notification provider.
This tells you that the terminal's reporting channel has gone quiet, so you can check the VPS, terminal, and connection. For the broader account picture, see monitoring multiple accounts. For risk while a robot is still trading, see drawdown control.
Prevention checklist
- Configure reliable VPS and terminal startup after a reboot.
- Confirm that the intended chart and robot load after restart.
- Enable connection-loss alerts as well as trade alerts.
- Check automated-trading permissions after a terminal restart.
- Prepare a downtime procedure, including how to inspect or manage open positions manually.