Appearance
Trade Execution Issues
A signal arrived but the trade did not open, opened with the wrong size, or behaved unexpectedly. Almost every case comes down to one of a handful of causes, and you can identify which in under a minute. Work through the checks in order — the first two catch the majority of cases.
First, check: is the account halted?
The single most common reason a signal does not execute is that the account hit its Risk Limit and is halted. While an account is halted, TTMT blocks every new signal-driven trade on it.
How to tell: the header shows halted under the account name, the account card in the account picker reads Halted by your daily loss limit (or a profit-target or risk-limits variant), and the daily loss chip reads HALTED. On a narrow screen the chip is hidden; open the user menu and choose Risk limits.
WARNING
A halt blocks new trades. With the default Stop new trades setting it leaves your existing positions alone; with Stop and close everything it also closes them when it fires. Resuming is one click — but read I'm Halted — What Now? first so you know whether to Resume or Recalibrate.
The halt is per-account: one halted account does not stop your others. If the next several signals on one account show nothing while your other accounts trade fine, the halt is almost certainly why.
Is trading paused on the account?
If you turned Trading active off for the account (the switch on the current-account card in the header's account picker), every new signal on it is skipped for that account. The account button reads trading paused. If another account the signal could go to is still active, the Signal Log shows the signal and lists the paused account. If every account the signal could go to is paused, the signal is not recorded in the Signal Log; you get a notification instead, at most one every 5 minutes. Turn the switch back on to trade again. Nothing was closed while it was off; see Pause trading.
Is the channel running on the account?
The second-most-common cause. A signal only fires if the channel is Running on at least one account. Go to Channels and look at the channel's line for the target account (or open the channel to see its accounts table): it should read Running, not Paused, Paused by plan, Halted or Not on this channel.
A paused channel silently ignores signals on that account. The channel itself is never "switched off"; the per-account line is what controls whether signals flow to that account. So a channel can look connected while its signals quietly go nowhere because it is paused there or was never added to that account.
Pausing a channel on an account stops new trades from it there. Trades already open keep their breakeven, trailing stop, TP redistribution, order timeouts and daily limits, and pending orders stay open. The channel's own close, modify and SL messages are not applied while it is paused, and they are not replayed when you resume. Nothing is closed or cancelled by the pause itself.
Signal not executing — full checklist
After the two checks above, walk through the rest in order:
- Account halted? See the section above — halted in the header.
- Trading paused, or channel not Running? See the two sections above — a paused account, a paused channel or a missing assignment ignores signals.
- Health word. Confirm the account button in the header reads OK (or Closed while the market is closed) and that the Telegram control is not showing a warning. If not, fix the connection first — see Connection Issues.
- Find the message in the Signal Log and read its status. Each status tells you a different story:
- Skipped — valid but intentionally not run: a duplicate, a close instruction for a trade you don't have, or a partial close too small for your lot size to express. See Signal Issues.
- Failed — TTMT couldn't build a trade from the message, or hit a broker error. See Signal Issues and Error Messages.
- Rejected — a safety check stopped it. See Signal Issues.
- Ignored — the channel is not Running on any account. See the channel check above.
Signal Issues covers the deep dive on each status.
The signal was skipped, not queued
A signal can be intentionally skipped the moment it arrives — and when that happens, no order is placed and the signal is not held for later. It's recorded in the Signal Log with a reason so you can see exactly why. Three common causes:
The market was closed. If a signal arrives while your broker's market for that instrument is closed, TTMT rejects it immediately — it does not queue the trade to fire when the market reopens. A broker-closed market is a neutral state, not a lost connection; a countdown to reopen is a display aid, not a promise that the signal will run then. If you want a channel's off-hours signals to trade, you have to be watching a market that's actually open.
A blocked-hours schedule was active. If you set up blocked trading hours (on the account, on the channel, or through a preset), a signal that lands inside a blocked window is skipped, not queued — same as market-closed. Blocked windows are periods trading is paused, and account and channel blocks combine, so a window blocked by either one blocks the signal. Check the channel's Setup › Which signals are taken › Trading hours and your account's Settings › Trading hours if signals go quiet at predictable times of day.
A blacklisted term matched. Channels can carry a text blacklist — a list of terms that, if they appear in a message, stop it before it's ever read as a signal. A matched message is skipped with a blacklist_match reason in the Signal Log. Replies are exempt, so close/modify follow-ups still work even if the original wording would have matched. If a channel's signals suddenly stop trading, check its Setup › Which signals are taken › Skip posts containing for a term that's catching them. See Signal Issues.
Wrong lot size
TTMT never uses the lot size written in the signal. It always computes volume from your own settings. If the size is wrong, work through these in order:
TIP
TTMT ignores the lot size in the signal entirely. Your size always comes from your own settings and caps.
- A preset on the channel is replacing your account's default lot size. Open the channel and check the Preset column for that account in its accounts table. If it reads By topic, the account uses topic rules: open Topic rules… to see which preset the signal's topic uses.
- Per-asset SL/TP defaults are not a volume override. They only set fallback stop-loss and take-profit distances for that asset class — they never change your lot size. Don't look here for volume.
- Platform volume backstop. TTMT applies a safety ceiling on total trade volume so a parsing glitch or oversized setting can't place a position far larger than the account could survive. If a computed size would exceed it, the trade is clamped down.
- Volume is split across your orders. Your total size is divided across the orders TTMT places. You choose how many layers to split the entry into (1–6, default 4); TTMT then works out how many individual orders each layer needs from your lot size and your broker's minimum lot and lot step — more size means more orders, capped at 6 per layer and 36 in total. So each individual order is smaller than your total, and the exact count depends on your size, your layer settings, and your broker's symbol rules. That's why a single order looks tiny next to your configured size. See Order Execution.
- Broker minimum. If a per-order size falls below your broker's minimum lot (often 0.01, but your broker's own minimum and lot step are what count), the order rounds against the broker's rules or, if it can't, fails with an invalid-volume error. This is also why very small balances produce fewer orders than you might expect — there simply isn't the size to split further. See Error Messages.
Breakeven not activating
The trade hit the trigger take-profit but the stop-loss did not move to entry. Common causes:
- Breakeven set to Never — check Auto-Breakeven in Settings › Protect open trades; it must name a TP level (TP1 to TP6), not Never. Never turns off Auto-Breakeven only; Breakeven once in profit is a separate setting.
- Wrong trigger level — if breakeven is set to trigger on TP2, hitting TP1 won't fire it.
- Fast market — price hit the trigger and reversed before the broker processed the stop-loss move. TTMT writes the intended stop and retries, but extreme volatility can occasionally outpace it.
- A preset on the channel, or a forum topic's own preset, is replacing your account breakeven setting.
Breakeven once in profit not firing
You turned on Breakeven once in profit, but the stop did not move. Check these in order:
- No value — the setting needs a value in When profit reaches. The trade's timeline then reads "Breakeven once in profit not checked — no value is set for it."
- No fill yet — it waits until the first order fills.
- The distance is not reached — profit is measured from the worst filled entry, using the bid for a buy and the ask for a sell. On a BUY with fills at 1.1000 and 1.0990, 15 pips means a bid of 1.1015, not 1.1005. On a SELL with fills at 1.1000 and 1.1010, it means an ask of 1.0985.
- R can't be measured — the timeline reads "R can't be measured: TTMT has no record of this trade's stop at its first fill." This happens for trades opened before this setting existed, and for trades whose first order has had no stop yet. If the stop at the first fill was at the worst entry, it reads "R is zero".
- No contract size or rate for money — money is checked only when TTMT knows the contract size and a currency rate for the symbol. The timeline then reads "TTMT doesn't know the contract size or a currency rate for EURUSD right now." Pips or R avoid this.
- It already fired — it fires once per trade. Orders that fill after that get no move from it. Auto-Breakeven, or Lock in profit at each TP, can still move their stop.
- Trailing or changed positions — it leaves trailing positions alone, and positions whose stop you changed yourself.
- A preset on the channel sets its own value, or turns it off.
Lock in profit at each TP not moving the stop
You turned on Lock in profit at each TP, but the stop stayed where it was. Check these in order:
- No breakeven source — it needs Auto-Breakeven set to a TP, or Breakeven once in profit on. Otherwise the switch reads "Not active: this needs Auto-Breakeven, or Breakeven once in profit. Your choice is kept."
- Breakeven is not set yet — stop moves start once breakeven is set. With breakeven at TP2, nothing moves at TP1.
- No earlier TP to go to — with Previous TP, there is no earlier TP at TP1, so the stop goes no further than breakeven there. With 2 TPs earlier, it goes no further than breakeven until TP3.
- A TP with no price — a runner TP never moves the stop, and only TPs with a price count.
- Nothing left open — at the last TP the remaining lots close, so there is no stop to move.
- You changed the stop yourself — TTMT then stops moving it on that position.
- The move is waiting — if a move can't be placed, the stop stays where it is and TTMT tries again every few seconds. The timeline shows it, for example "Move to TP2 waiting — The broker won't accept 1.1040 this close to price." It never closes a position for this.
- A preset on the channel sets its own value, or turns it off.
A channel stop move that was not applied is a different case: while the setting is on, a channel stop move that would loosen your stop is not applied, and the timeline says "Channel stop move not applied".
Trade opened but no SL or TP
The signal had no stop-loss or take-profit and you have no defaults configured. Fixes:
- Set Stop loss when the signal has none in Settings › Stop loss and Take profits when the signal has none in Settings › Take profits, or per symbol or asset class under Symbol exceptions.
- Check your If the signal's stop looks wrong choice (Use my stop or Trust the signal) and When a signal's prices look wrong (Correct them, Skip the signal or Use as sent).
- For channels that consistently omit SL/TP, give it a preset with stricter defaults.
For the full breakdown of missing-SL/TP cases, see Signal Issues.
Orders stuck in pending
This is usually expected, not a bug. Layered entries place limit orders below market (for a BUY) or above market (for a SELL), and they only fill when price reaches them. If price runs in your favor immediately, the deeper layers may never fill — that is by design.
INFO
Pending limit orders that never fill are not lost trades — they were entries waiting for a retracement that didn't happen. Layer 1 (placed at market) is what gets you into the move.
You can read the entry price for each order in the trade detail. TTMT automatically cancels pending orders when the stop-loss is hit (orphan cancellation), when you configured cancel-at-TP, or when the trade is closed manually or by a signal.
One thing that can surprise you: with the Layer-1 lock on (the default), once a deeper layer fills, Layer 1's target moves to TP1 to secure break-even (on Most at last TPs, except its largest order). That is why a pending-heavy trade can suddenly show a near take-profit. See TP Redistribution.
Automatic safety pause (circuit breaker)
After repeated execution failures on one account, TTMT's circuit breaker temporarily pauses new attempts so that a broken connection or a broker outage doesn't burn through orders. There is no banner or indicator with this name in the dashboard; you notice it as signals on that account waiting instead of trading, and it may coincide with a connection problem. It is not the same as Pause trading or a Risk Limits halt, which you can see in the header.
What happens next: the pause lifts on its own. TTMT re-tests automatically after a short cool-off (about 30 seconds), and trading resumes once attempts start succeeding again.
One important correction: failures that are not the broker's fault do not count toward the pause. A closed market, a rate-limited request, or a position the broker briefly hadn't surfaced yet are all excluded. The pause only builds from real execution failures.
If the pause keeps re-tripping, the root cause is almost always connection or broker-side — see Connection Issues.
Per-account isolation
Each MetaTrader account has its own independent safety pause and its own halt state. One account's pause or halt never affects the others.
Examples
- Halted prop account. You're three trades into the London session, your $50k prop account hits its daily-loss limit, and the next four signals show nothing on the dashboard. The account is halted — see halted under the account name in the header. Without Risk Limits, those four signals would have kept trading you past the prop firm's hard breach line and failed the challenge.
- Channel not on the account. You followed a new channel last week but never added it to your live account. Its signals show as Ignored because the channel is not Running on any account.
- Wrong lot size from a preset. Your account default is 0.50 lots but trades from one channel keep opening at 0.20. That channel uses a conservative preset that replaces the account default.
- Volume cap. A computed size balloons far past what your account should ever place — a parsing glitch or an oversized setting — and TTMT clamps it down to the platform's safety ceiling instead. Without the backstop, that glitch could have placed a position far larger than the account could survive.
- Pending that never fills. A BUY EURUSD fires, Layer 1 fills at market, price runs up 30 pips, and Layers 2–4 sit pending forever. They were waiting for a retracement that never came. That is normal.
- Safety pause. Your broker's server goes down mid-session. After a few failed orders, new attempts on that account wait. Ten minutes later the broker is back and trades resume on their own — you did nothing. Without the pause, TTMT would have hammered a dead connection on every signal.

