TTMT Docs

Appearance

Signal Issues ​

Every message from your monitored channels goes through reading, safety validation, duplicate detection, and routing before it can become a trade. When a signal does not turn into the trade you expected, the Signal Log tells you which stage stopped it. This page maps each Signal Log status to its cause and fix, then covers the trickier "it executed, but not how I expected" cases.

TIP

The Signal Tester is your single best tool here: paste any signal and see exactly what TTMT read, which checks pass or fail, and what the trade would look like — with no money at risk.

Signal Failed (couldn't be read) ​

The signal shows as Failed with a reading error. This means the message format wasn't recognized as a trade, or it wasn't a signal at all — commentary, chat, or an image.

Fixes:

  1. Read the raw text. Click the failed signal to view the original message and confirm it actually contains a direction, symbol, entry, stop-loss, and take-profit.
  2. Test it. Paste the message into the Signal Tester to see exactly what the AI signal reading detected and what it missed.
  3. Persistently failing channels. If one channel consistently fails to read, it may need a custom signal-reading prompt. These are set per channel by the TTMT team, so contact support with examples of the channel's format.
  4. Unusual formatting. Very uncommon languages or heavy emoji and special-character formatting reduce reading accuracy.

Signal Rejected (caught by a safety check) ​

The signal was read correctly, but a safety check stopped it. Click the signal to see which check fired:

  • SL on the wrong side — the stop-loss is above entry on a BUY (or below on a SELL). Check your invalid-SL handling setting.
  • SL too far — the stop-loss is more than 5× the distance to the farthest take-profit. That pattern usually means a mistyped price, so TTMT protects you from an oversized stop. Verify the signal before loosening anything.
  • TP on the wrong side — wrong-side take-profits are removed automatically. If every TP is removed, the trade may fail.
  • Entry zone invalid — the zone is inverted (low above high) or implausibly wide relative to the stop distance. Usually a typo — test it in the Signal Tester.
  • Extreme values — a price sits far outside any trustworthy reference, for example a decimal shift like 1.085 arriving as 10.85. TTMT either replaces the value from a trusted anchor or rejects the signal. Adjust your extreme-value handling if you want to override.

INFO

Rejections are TTMT refusing a signal that looks wrong. They protect you from typos and decimal slips in the original message.

Signal Skipped (valid but intentionally not run) ​

The signal was valid but TTMT chose not to run it. Click it for the skip reason:

  1. Duplicate — an identical signal already ran. This is expected.
  2. Close or modify instruction for a trade you don't have — common right after you join a channel mid-stream and the close instruction refers to an earlier entry you never took.
  3. Symbol filtered out — that instrument is excluded for this channel. Check the channel's Symbols tab.

Signal Ignored (no active route) ​

The message never reaches execution. The cause is almost always that the channel has no active account assignment, or the message isn't from a monitored channel. Fixes:

  1. Confirm an active assignment. The channel needs at least one active account assignment. A paused assignment ignores signals — the channel itself is never "switched off"; the per-account assignment controls whether signals flow to that account.
  2. Confirm the channel is added in TTMT, not just joined in Telegram.
  3. Check the execution mode. In Complete Only mode, an alert-only message (direction and symbol, no entry/SL/TP) won't run. Switch to Execute on Alert if the channel alerts first and sends details later. See Execution Modes.

Wrong symbol detected ​

The signal mapped to the wrong instrument, or to none at all. TTMT matches the signal's symbol to your broker's instrument list with a four-step approach:

  1. Exact match.
  2. Suffix/prefix strip — EURUSDm and EURUSD.raw both resolve to EURUSD.
  3. Alias groups — GOLD resolves to XAUUSD, US30 resolves to its index equivalent, across 20 predefined alias groups.
  4. Normalized-base fallback for minor formatting differences.

Fixes:

  1. Check Symbol Mapping to see how the symbol resolved.
  2. Add a manual map to override automatic matching for that symbol.
  3. If you recently switched the account to a different broker, re-run the symbol refresh so mappings re-validate against the new broker's list.
  4. Test in the Signal Tester before it hits the live account.

See Symbol Mapping.

Missing SL or TP ​

The signal was read correctly but has no stop-loss or take-profit because the channel omitted them. Fixes:

  1. Set default SL/TP pip values per asset class in your settings.
  2. Set per-channel SL/TP defaults on the channel's SL-TP tab.
  3. For channels that always omit, assign a Config Profile with the right defaults.
  4. Two-phase channels (alert first, details later) need Execute on Alert mode. In Complete Only, TTMT waits for one message with all values. See Execution Modes.

"It executed at a price I didn't expect" ​

The trade opened, but the entry, stop, or target wasn't what the signal printed. There are three common, deliberate reasons.

WARNING

If you use SL/TP overrides, the executed levels come from your settings, not the signal. Check your override settings before reporting a "wrong" fill.

Trade filled just outside the printed zone (entry-zone expansion). TTMT widens the Layer-1 side of the entry zone by a small margin so a near-miss price still gets you in rather than missing the move entirely. If a fill looks a pip or two outside the stated zone, this is why. It only widens the favorable side, and only by your configured expansion amount. See Entry Zone Expansion.

Your SL/TP override changed the levels (override modes). If you turned on stop-loss or take-profit overrides, TTMT applies your own levels instead of the signal's, and resolves the entry zone first so the override anchors to the right price. There are two ways the entry zone can be handled — a fixed mode using your exact pip distances, and an auto mode computed at fill. If the resulting stop or target differs from the signal's printed values, your override is doing exactly what you set it to. See Override Modes.

A zone-only "limit" signal placed as a limit, not at market (single-layer). With one entry layer configured, a signal that gives only a price zone (no single entry) places a limit order at the favorable edge of that zone instead of firing at market. If you expected an immediate market fill on a one-layer setup and got a resting limit instead, this is the reason. See Limit Order Conversion.

Examples ​

  • Failed read. A meme- and emoji-heavy message that wasn't a signal at all shows as Failed — there was no trade for TTMT to build.
  • SL too far. A gold signal arrives with the stop-loss mistyped 5× past the farthest take-profit. TTMT rejects it before placing an oversized stop. Without the check, a fat-finger SL becomes a real, huge-risk position.
  • Extreme-value catch. A decimal shift — 1.0850 sent as 10.850 — is replaced from the live price anchor. Without sanitization, the trade would have used a price 10× off.
  • Ignored signal. You joined a channel in Telegram but never added or assigned it in TTMT, so every signal shows as Ignored.
  • Entry-zone-expansion fill. The zone was 1.0850–1.0840, price ticked to 1.0851, and TTMT still filled Layer 1 — the expansion caught the near-miss. Without expansion, the signal would have been missed by a single pip.
  • Override surprise. Your take-profit override is set to fixed 30/60/90 pips, so a signal that printed TP at 1.0900 instead took profit at your 30-pip level — your override, working as configured.