---
url: /troubleshooting/signal-issues.md
description: >-
  Why a signal failed, was rejected, skipped, or ignored — plus blacklist
  filters, teaching a channel, the Parse Lens, per-account outcomes,
  wrong-symbol detection, missing SL/TP, and trades that executed at a price you
  didn't expect.
---

# 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 **If the signal's stop looks wrong** setting (**Settings › Stop loss**).
* **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. Change **When a signal's prices look wrong** (**Settings › Signal checks**) 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 not in your allowlist** — that instrument isn't in this channel's symbol allowlist, so it's excluded. Check the channel's **Setup › Which signals are taken › Symbols**.
4. **Blacklisted term matched** — the message contained a term on the channel's text blacklist and was stopped before it was read. The reason reads `blacklist_match:<term>`, naming the term that caught it. See [Blocked by a blacklist term](#blocked-by-a-blacklist-term) below.
5. **Market closed** — the signal arrived while your broker's market for that instrument was closed. It's skipped immediately, not held for reopen. See [Trade Execution Issues](/troubleshooting/trade-execution-issues#the-signal-was-skipped-not-queued).
6. **Blocked hours** — the signal landed inside a blocked trading window you configured (on the account, the channel, or a preset). Also skipped, not queued.
7. **Partial close too small to place** — the channel asked for a partial close your position can't express. Closing 50% of a single 0.01-lot position means 0.005 lots, which is below every broker's minimum, so there is nothing valid to send. On a minimum-lot position the only two things TTMT can do are close all of it or none of it. It skips rather than closing the whole position, because silently exiting a trade you were told to trim is the more expensive mistake. If the same message also said to move to breakeven, **the breakeven still applies** — you'll see that in the skip reason. Size up if you want partials to work: a 0.05-lot position can be trimmed, a 0.01-lot one cannot.

## Signal Ignored (no active route)

The message never reaches execution. The cause is almost always that the channel is not **Running** on any account, or the message isn't from a monitored channel. Fixes:

1. **Confirm the channel is Running on an account.** On the Channels page the channel's line for each account reads **Running**, **Paused**, **Paused by plan**, **Halted** or **Not on this channel**. A paused channel ignores signals on that account — the channel itself is never "switched off"; the per-account line controls whether signals flow to that account. A channel pause does not mark the held-back messages as skipped in the Signal Log, so an empty stretch in the log can simply be a pause. While a channel is paused on an account, its breakeven, trailing stop, TP redistribution, order timeouts and daily limits keep running on trades already open, and its close, modify and SL messages are not applied there.
2. **Confirm the channel is added in TTMT,** not just joined in Telegram.
3. **Check the execution mode.** In **Wait for Full Signal** mode, an alert-only message (direction and symbol, no entry/SL/TP) won't run. Switch to **Trade on First Alert** if the channel alerts first and sends details later. See [Execution Modes](/channels/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 a curated set of alias groups (currently around 20), plus dedicated Gold and Bitcoin handling.
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](/accounts/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** in **Settings › Stop loss** (**Stop loss when the signal has none**) and **Take profits when the signal has none** in **Settings › Take profits**, or per symbol or asset class under **Symbol exceptions**.
2. **Set per-channel SL/TP defaults** on the channel's page under **Setup › Stop loss & take profit**.
3. **For channels that always omit,** give it a preset with the right defaults, or set its fallback SL/TP in the channel's Setup.
4. **Two-phase channels** (alert first, details later) need **Trade on First Alert** mode. In **Wait for Full Signal**, TTMT waits for one message with all values. See [Execution Modes](/channels/execution-modes).

## Blocked by a blacklist term

A channel can carry a **text blacklist** — a list of terms that, when they appear in a message, stop it before it's read as a signal at all. This is how you mute a channel's non-trading noise ("scalp session starting", "results", promo posts) without unfollowing it.

* The list holds up to 100 terms, each up to 200 characters. Matching is case-insensitive and whitespace-normalized, and it matches whole terms — so `scalp` blocks a message that says "scalp" but not one that says "scalpel."
* A matched message is skipped and logged with a `blacklist_match:<term>` reason, so you can see exactly which term caught it.
* **Replies are exempt.** A reply to an earlier signal (a close, a modify, "move SL to entry") still goes through even if its wording would otherwise match, so your follow-ups keep working.
* If matching ever fails internally, it fails open — the message is let through rather than silently dropped.

If a channel's signals suddenly stop trading, open its **Setup › Which signals are taken** and check **Skip posts containing** for a term that's catching them. The allowlist (**Symbols**) and the blacklist both live there and apply on all your accounts, but they do different jobs: the **symbol allowlist** decides which instruments may trade; the **text blacklist** is channel-wide and decides which messages are even read. See [Message filters](/channels/message-filters).

## "Teach this channel" (suggest a correction)

When a channel is consistently misread — the wrong direction, a missed take-profit, a value pulled from the wrong place — you can teach TTMT how that channel's signals should be understood.

1. In the Signal Log, open the signal that came out wrong and choose **Suggest a correction**.
2. In the **Teach this channel** sheet, fix what's wrong: the classification (is this actually a signal? an alert? a close?) and/or the extracted fields (entry, SL, TPs, symbol, direction).
3. Submit it for review.

::: info Submitting doesn't change parsing right away
A correction goes to the TTMT team for review; it doesn't retrain the channel the instant you submit. Improvements are applied when the review is approved and the teaching feature is switched on for that channel. Treat it as feedback that makes the channel better over time, not a live edit — and keep using the **Signal Tester** to check how signals read in the meantime.
:::

## Parse Lens and per-account outcomes

Open any signal from the Signal Log to see the **Parse Lens** — the signal view that shows the raw message next to what TTMT actually extracted, with plain-English notes on each field and why any validation adjusted it. It's the fastest way to answer "what did TTMT think this signal said, and why."

Because one signal can [broadcast to several accounts](/accounts/account-broadcasting), the same message can end differently on each — executed on one account, skipped on another (paused assignment, symbol not in that account's allowlist, that account halted), rejected on a third. The signal view breaks the outcome out **per account**, so a signal that "didn't trade" on one account but did on another isn't a contradiction — it's the per-account picture. Read the per-account outcomes before assuming a signal failed everywhere.

## "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 turned on **Always use my stop, not the signal's** (or the matching take-profit or zone toggle), 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 amount (**Widen by**). See [Entry Zone Expansion](/core-concepts/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](/core-concepts/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](/core-concepts/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.

## Related pages

* [Trade Execution Issues](/troubleshooting/trade-execution-issues)
* [Error Messages](/troubleshooting/error-messages)
* [Message filters](/channels/message-filters)
* [Symbol Mapping](/accounts/symbol-mapping)
* [Execution Modes](/channels/execution-modes)
* [Entry Zone Expansion](/core-concepts/entry-zone-expansion)
* [Override Modes](/core-concepts/override-modes)
* [Limit Order Conversion](/core-concepts/limit-order-conversion)
* [Signal Tester](/dashboard/signal-tester)
