A silent trading screen is a symptom, not a diagnosis. The message may never have reached the copier, a rule may have deliberately skipped it, or the broker may have rejected an entirely sensible request. Reconnecting everything at once destroys the evidence and can leave the original instruction waiting to execute beside its replacement.
Start with one identifiable message and follow it through the route. Record its chat, time and message identifier where available, then compare the processing record with the destination's order history. Before retrying, establish whether an order already exists; an absent position does not mean an absent pending order.
In this guide
Establish what actually arrived
Check that the Telegram session can still access the selected source and that the saved configuration points to that chat. Similar channel names are common, and a discussion group is not necessarily the channel whose posts you intended to copy. A phone notification proves your phone received something; it does not prove the copier's session received the same event.
Use a recent, unambiguous demo message when testing access. An old post, a forwarded screenshot and an edited message can have different event handling, so changing all three variables is a poor diagnostic experiment. Keep the original evidence and vary one thing at a time.
Separate interpretation from permission
A parser can understand a message that the route is configured to skip. Requirements for protective levels, symbol restrictions, disabled market entries and duplicate detection can all prevent execution without constituting a failure. Compare the extracted fields with the actual saved rules, rather than with settings you remember entering.
The signal-format guide helps distinguish an entry instruction from commentary or a result announcement. A post saying “TP1 reached” is not automatically a new buy order. Treating every skipped message as a defect is an excellent way to manufacture defects.
| Last confirmed stage | Next evidence to inspect |
|---|---|
| Source message exists | Session access and selected chat |
| Message received | Extracted instrument, side and levels |
| Instruction recognised | Skip reason and route settings |
| Request submitted | Connector response and destination history |
| Order accepted | Pending status, fill, cancellation or rejection |
Read the destination's answer
An unknown symbol, invalid quantity increment, insufficient margin or closed session requires a different correction from a disconnected terminal. Preserve the actual rejection text. “It did not trade” conceals the useful part of the conversation with the broker.
For MT5, inspect the terminal and EA connection as well as the web dashboard. For an API route, check authorisation, selected account and the permissions required for that market. The symbol-mapping article explains why a correct-looking market name may still be an invalid execution symbol.
Investigate doubles before adding a filter
Two trades can result from two source posts, two enabled routes, intentional target allocation or an uncertain retry. Count the requests and their origin before deciding that the parser duplicated a message. A duplicate window cannot serve as a universal one-position-per-symbol policy, and increasing it may suppress a legitimate later entry.
Reconcile the original message, each route and every resulting order in a small incident record. Include the settings active at the time; today’s corrected settings cannot explain yesterday’s behaviour. When requesting support, remove credentials and session codes while retaining timestamps, non-secret configuration and the destination error.
Restore one controlled path
After correcting the cause, test the complete lifecycle on demo: entry, protective levels, intended management and closure. Confirm the resulting quantity and account, not merely a green connection indicator. A connection test establishes that two machines can talk; an execution test establishes what they said.
Leave retries disabled until you understand the state of the original order. For delays rather than missing instructions, use the latency guide to locate the slow stage instead of repeatedly submitting the same trade.
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