Three Silent Failures That Stop Automated Trading
A working automated trading setup has three things that can stop it silently while you are at work, asleep, or otherwise not looking. The terminal goes offline. The alerts stop firing. The broker rejects the orders. None of these announce themselves. They just stop. Here is how each one happens, how to confirm it from your logs, and what prevents it from happening again.
What Happens When the Terminal Goes Offline?
The terminal is the MetaTrader 5 process running the PineConnector EA. If it stops, alerts from TradingView have nowhere to land. No trade is placed, and no error appears in TradingView because the webhook was delivered successfully. The failure is invisible from the alert side.
The most common cause is a machine that goes to sleep. When a laptop sleeps, it closes or suspends the MT5 process, so alerts that fire during that window are delivered and lost. When the machine wakes, MT5 reconnects and the system looks fine again. The gap of missing trades is indistinguishable from a quiet market.
How to check :
Compare your TradingView alert history against the MetaTrader fill log for the period in question. Alerts that fired with no matching fill, during open market hours, mean the terminal was down when they arrived.
A VPS runs continuously, so it avoids the sleep problem, but it has its own failure modes. It can lose its remote desktop connection while the process keeps running, or restart after a provider maintenance window and come back with MT5 closed, depending on how startup is configured.
PineConnector Edge removes this category of failure. The managed terminal runs in PineConnector's cloud, not on a machine you own or rent. You enter your own broker credentials and control the terminal from the portal, and PineConnector staff never see or handle your login. It stays running because keeping it online is part of the service, not part of your morning checklist.
| Terminal Setup | Sleep Risk | Restart Risk | Your Morning Check |
|---|---|---|---|
| Laptop | High | High | Check MT5 is open and connected |
| VPS (self-managed) | Low | Medium (provider windows) | Check MT5 is running after any restart |
| PineConnector Edge | None | None | Confirm terminal is active in the portal |
What Happens When Alerts Stop Firing?
TradingView alerts have a rate limit of 15 triggers per 3 minutes. Exceed it and TradingView disables the alert to prevent overloading, so it stops sending webhooks silently. Alerts also stop when they expire, when they are paused after a delivery failure, or when an expiry set at creation is forgotten. Your Pine Script keeps generating signals on the chart, but nothing reaches MetaTrader.
How to check :
Open the Alerts panel in TradingView and look at each alert's status. One that should be firing but shows as paused or expired is your answer. Recreate it with no expiry date once the setup is confirmed. One related cause is a Pine Script change: existing alerts keep running against the script version from when they were created, so recreate the alert after any script update.
What Happens When the Broker Rejects the Order?
An order rejection is the hardest to catch because it happens after PineConnector processes the alert. PineConnector sends the instruction to MetaTrader, MetaTrader sends the order to the broker, and the broker rejects it. The rejection lands in the MetaTrader journal as an error code, but nothing shows in TradingView and no notification fires unless you set one up.
The common causes are a symbol name mismatch between TradingView and your broker, a lot size outside the broker's allowed range, insufficient margin, and market hours restrictions. Any of these can sit in a working setup for weeks until the exact condition that triggers it arises.
Symbol mismatches are the most frequent. Your broker may name a symbol differently from TradingView, so XAUUSD might need to be GOLD or XAUUSD. at your broker. The error only appears when an alert fires for that symbol, so if you tested with EURUSD and run live on XAUUSD, the first live XAUUSD alert is when you find out.
How to check :
Open the Experts tab and Journal tab in MetaTrader after each session and look for error codes. An error 4106 or a symbol not found message is a symbol mismatch. Error 4756 is an unsupported filling mode. The PineConnector Error Guide covers the common error codes and their fixes, and the FAQ explains how to open the Journal and Experts logs for the exact error.
How to Catch All Three Before They Cost You
The most reliable method is a short daily check against three data points. Confirm in your TradingView alert history that alerts fired when the strategy should have signalled. Confirm in your MetaTrader fill log that fills appeared for those alerts, and compare the two for any session where you expected activity but see none. That catches the terminal-offline and alert-stopped cases. Then scan the MetaTrader journal for error codes, which catches broker rejections. It takes five to ten minutes and points you straight at the failure when something stops.
FAQ
How do I know if my terminal went offline overnight?
Compare your TradingView alert history against your MetaTrader fill log. Alerts that fired in TradingView but have no matching fill in MetaTrader, during open market hours, mean the terminal was not running when the alert arrived.
Can TradingView tell me if my webhook failed?
TradingView only confirms that the webhook was delivered to the URL, not that the order was executed. A successful delivery is consistent with a terminal that was offline when it arrived.
How do I stop my VPS from restarting MT5 in a closed state?
Set MT5 to start automatically with Windows using the startup folder or a scheduled task, then restart the VPS once to confirm MT5 opens and the EA loads on its own.
What is the easiest way to fix the alert expiry problem?
Set the expiry to an open-ended alert rather than a specific date, and review your active alerts monthly to confirm none have been paused.
How do I fix a symbol name mismatch?
Check the exact symbol name in your broker's MetaTrader symbol list, then update the symbol field in your TradingView alert message to match. Test with a demo account before updating a live alert.
Does PineConnector Edge prevent all three of these failures?
It prevents the terminal-offline failure. Alert configuration and broker symbol mapping remain your responsibility regardless of how the terminal is hosted.
Next step: Start with Core and send your first automated trade from TradingView to MT5 today. If you are weighing up what day-to-day management looks like once a system is running, The Morning Routine of a Trader Who Works 9 to 5 covers the full picture.
Reviewed 22 September 2026. Facts were checked against the linked sources on that date.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
