TelegramSignal can interpret a message in the cloud while MT5 executes through an Expert Advisor in your terminal. Those are separate parts of the connection. Closing the computer that runs the terminal can interrupt the execution side even though the Telegram source remains connected elsewhere.
Start by identifying the exact terminal and broker account intended to receive orders. A desktop with several installations is remarkably good at making the right settings disappear into the wrong window. Demo and live environments deserve names you can distinguish without relying on memory.
In this guide
Put the EA on the machine doing the work
AlgoWay's MT5 installation guide describes the official installer, required terminal permissions and route identifier used by the EA. Install on the machine where that terminal actually runs, attach the EA as instructed and verify its connection in the Experts tab. Installing locally does not configure a separate VPS terminal.
Keep installation and strategy configuration separate. First establish that the official EA is loaded, allowed to operate and connected to the intended route. Then review the quantity, symbol and position settings; changing all of them while debugging a missing connection makes the evidence unnecessarily muddy.
Give the instrument its broker name
The provider's XAUUSD may not be the symbol your account trades. Open Market Watch and inspect the broker's available instrument and specification before applying symbol mapping. A suffix can indicate a different offering, so do more than check whether the chart draws roughly the expected price.
The specification also defines quantity increments and price properties. A displayed decimal is not necessarily the trading increment, and the meaning of a pip in a Telegram message must be established separately. The gold-copying guide explains why that distinction matters particularly often on metals.
Check the first ticket with numbers attached
Use a demo account and a message whose expected action you have written down. Compare the final order quantity, entry type, stop and target with that record. A destination accepting the request proves only that the request was valid there; it does not prove that your intended quantity survived every setting correctly.
| Evidence | What it helps establish |
|---|---|
| Original Telegram message | The instruction the provider supplied |
| AlgoWay route record | The message and execution response for that route |
| MT5 Experts and Journal | EA activity, connection and terminal errors |
| Order and deal history | Accepted orders, actual fills and prices |
Do not confuse orders with deals. A pending order can exist without a fill, while an executed trade produces history that should be inspected at the account. Use the terminal's record to settle the outcome rather than a message-received notification.
Existing positions change the question
An opposite signal arriving into an empty account is a simpler test than the same signal arriving while exposure already exists. The account model and selected execution mode affect what happens next. Test those cases intentionally rather than assuming every SELL both closes the earlier BUY and opens a fresh short.
Multiple targets add another layer. Confirm whether the configured route creates several orders and how their total quantity compares with the original signal. Our multi-target explanation provides the arithmetic needed to distinguish an intended split from accidental multiplication.
Keep the running environment boring
The terminal must remain available for the EA-based part of the workflow. Sleep, a lost broker session or an interrupted connection can break that chain; the correct remedy depends on where the interruption occurs. A VPS can host the terminal, but it does not remove the need to observe its state.
Read cloud versus VPS before deciding what you can switch off. When a signal fails, follow the diagnostic sequence rather than reinstalling everything first. A stable, understood terminal is more valuable than a frequently rebuilt one.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay