Appearance
A signal did not trade
Follow the message through each stage. A successful Telegram connection alone does not establish that a message was routed to a ready account or filled by the broker.
1. Find the received message
Open Signal Log and check the source and time. Clear restrictive filters and confirm your timezone. If the message is absent, check Telegram connectivity, source access and channel monitoring.
A successful Signal Tester run does not verify Telegram ingestion or channel routing.
2. Read the processing result
Open the message and inspect its original content, recorded edits and reason. Commentary, unsupported formats or incomplete messages may not produce a trade.
| Reason | Check |
|---|---|
| Required SL/TP missing | Supply the levels required by the applied profile. |
| Price tolerance exceeded | Compare the market movement with the profile's allowed tolerance. |
| TP targets and order count do not match | Check the signal targets and profile entry/order configuration. |
| Preview only | Execution was disabled; no live trade was submitted. |
| Unsupported signal format | Review the message and channel parsing settings. |
3. Check the intended account
Review each account result rather than only the message summary. Confirm source-to-account routing, account readiness, trading controls and its Applied profile version. Current settings may differ from those used when the signal arrived.
Signal completed means processing finished. It does not by itself confirm a fill. Account results differ means you must inspect each account separately.
4. Inspect the execution result
In Execution History, check Requests, related Placed orders and Fills. Review reasons such as market closed, unavailable symbol, unsupported volume or insufficient margin.
A pending order can be placed successfully without being filled. Check Pending orders in Trading.
5. Resolve uncertain outcomes before retrying
For Checking with broker, Needs review or interrupted updates, refresh and compare Trading, Positions and the broker terminal. Request receipt is not proof that nothing traded, and a timeout is not proof of failure.
Collect the safe error and support reference if the result remains unclear.