A Telegram message can be visible in a channel without becoming an MT5 order. That does not, by itself, tell you where the process stopped. The useful approach is to trace one message through receipt, processing, routing and broker execution—in that order—rather than changing settings or retrying immediately.
AutoMetaTrade’s troubleshooting guide recommends checking the message in Signal Log, reviewing its processing details, checking the receiving account and then inspecting Execution History. The distinction matters: a message may not have arrived, may have been rejected during processing, may not have been routed to an account, or may have produced an order that has not filled. This guide follows those steps to help you identify which explanation fits your case.
1. Look for the message in Signal Log
Start with the specific Telegram source and approximate time of the message. In Signal Log, use the relevant source, time range and filters to search for it. Make sure the selected source and time window match the message you are investigating; a narrow or incorrect filter can make a received signal easy to overlook.
If you find the message, open its details and continue to the processing and execution checks below. If it is absent, do not assume that MT5 rejected an order. First establish whether AutoMetaTrade received the message at all. The troubleshooting guide recommends investigating a missing message by checking source access, Telegram connectivity and channel monitoring.
A Signal Tester result is not evidence that a Telegram message was ingested or routed. Testing signal interpretation and tracing a real message through a channel are separate checks. For the documented investigation sequence, see Troubleshoot a missing signal.
2. If it is missing, check Telegram access and monitoring
Confirm that the Telegram connection is working and that the connected account or bot can access the intended source. For a personal Telegram connection, the account must be a member of the signal channel; if a channel is missing from the selection, the documentation advises confirming membership and syncing. A connected Telegram account alone does not establish that messages from a particular channel are arriving.
Next, check that the intended source is selected and that monitoring is healthy. These are separate from the Telegram connection itself. AutoMetaTrade’s Telegram connection guide explains the difference between connecting an account, selecting sources and checking monitoring.
Also inspect the channel’s receive source. A channel associates a Telegram source with zero, one or several MT5 accounts. If it has no receiving accounts, it can monitor messages without trading. Check the channel’s Setup to see which accounts are currently selected, and confirm any changes rather than assuming that saving a Telegram connection also configures account routing. See Channels: monitor sources and select receiving accounts.
3. If it appears, read the processing details
Finding a message in Signal Log confirms that it is present in the log; it does not mean that it was accepted as an actionable signal or sent to a broker. Inspect the original message, any edits and the recorded processing reasons. The documented examples include missing required levels, an unsupported format and price tolerance.
Compare the message with the parsing and order rules in the Trading Profile that was in effect for the receiving account. Do not assume that every language, layout, image-only message or management phrase is supported: parsing depends on configuration and capabilities. The availability guide specifically cautions against treating support as universal. If the message was edited, include that history in your review; the original and edited content may help explain why processing differed from what you expected.
A “completed” processing status is not the same as a broker fill. It may describe completion of a processing step, so continue to the execution records before concluding that a trade was placed. Avoid changing several profile settings at once while diagnosing one signal; first use the recorded reason to identify what needs checking.
4. Confirm routing, account readiness and the applied profile
For a signal that appears in the log, verify that the channel routes to the MT5 account you expected. Check each receiving account separately: having an account connected does not automatically select it as a destination for a Telegram channel. Channel destinations determine where the source is routed, while each account has its own readiness and confirmed Trading Profile.
Review the account’s connection and readiness. The MT5 guide says that account connection requires the account number, trading password and exact broker server; an investor password cannot execute orders. A successful connection is still not the same as confirmed trading readiness. Review the account’s applied profile and any relevant execution controls as well.
A saved Trading Profile version is not necessarily the version currently applied to an account. The documented workflow is to save a version, apply it to the intended account and wait for confirmation. Check which confirmed version was used for the signal rather than relying on the most recently edited settings. Channel destinations and account profiles are independent: routing a signal to an account does not replace that account’s confirmed profile. Details are available in Trading Profiles: preview, save and confirm applied versions and Connect MetaTrader 5 and verify execution readiness.
For a first-pass setup, AutoMetaTrade’s quick-start workflow lays out a sequence using one Telegram source, one demo MT5 account and one confirmed Trading Profile. The AutoMetaTrade website provides more information about the product. A healthy Telegram connection alone does not establish that the source is monitored, the account is routed or the account is ready.
5. Use Execution History to distinguish an order from a fill
Once you have checked the signal and its destination, inspect Execution History for the relevant account and message. Look at the execution details: the guide recommends checking requests, placed orders and fills. These are different events, and the record can show where the sequence stopped.
A successfully placed pending order may remain unfilled. In that case, an order was placed, but a filled trade has not yet been established. Conversely, a processing status alone does not establish that an order was placed. Use the execution records to distinguish these outcomes instead of treating every status as synonymous with “trade created.”
If sizing or broker validation appears relevant, review the effective stop loss, signal layout and broker checks. The risk documentation notes that broker volume steps, minimum and maximum volumes, and margin can matter. It also explains that an excessive maximum lot per order can lead to rejection rather than automatic clipping. These are possible checks—not a basis for assuming that any one of them caused a particular signal to fail. Use the recorded execution details to guide the investigation. See Risk and order sizing.
6. Refresh before retrying an uncertain outcome
If processing or execution was interrupted, timed out or is otherwise unclear, refresh Trading and Positions and compare the result with the broker terminal before trying again. A timeout does not prove that an operation failed; an order may have reached the broker even if the interface did not clearly confirm the outcome. Retrying without checking could therefore obscure what happened or create an unintended duplicate.
The troubleshooting guide specifically advises refreshing uncertain outcomes and comparing with the broker terminal. If Signal Log has no message, return to access and monitoring checks. If it has a processing reason, investigate that reason and the profile used. If it shows an execution request or placed order, verify the broker-side outcome before taking further action.
A practical checklist
For one signal, work through these questions in order:
1. Is the message in Signal Log when searched with the correct source, time and filters? 2. If not, can the connected Telegram account or bot access the source, and is monitoring healthy? 3. If it is present, what do the original content, edits and processing reasons show? 4. Is the intended MT5 account selected as a receiving destination, ready, and using the confirmed profile version expected for the signal? 5. What do Execution History and the broker terminal show: no request, a placed order, a fill, or an uncertain result?
That sequence helps separate a missing Telegram message from a parsing or routing issue, and both from an unfilled or uncertain broker outcome. It also avoids treating a connection, saved profile or completed processing step as proof of a filled MT5 trade.