Appearance
Are you an LLM? You can read better optimized documentation at /troubleshooting/error-messages.md for this page in Markdown format
Error Messages
This page is a comprehensive reference of error codes you may encounter in TTMT. Errors appear in the Signal Log, trade details, and notification messages. Each entry explains what the error means and how to resolve it.
Trading Errors
These errors occur during trade execution.
| Code | Message | Meaning | Fix |
|---|---|---|---|
RISK_TOO_HIGH | Calculated lot size exceeds limit | The trade requires a lot size larger than your account margin allows or larger than your volume cap. | Reduce your configured lot size, lower your risk percentage, or deposit more funds. |
SYMBOL_NOT_MAPPED | Symbol not found on broker | The signal used a symbol name that could not be matched to any symbol on your broker. | Add a manual map in Symbol Mapping. |
MARKET_CLOSED | Market is closed | TTMT tried to execute a trade outside of market hours (weekend, holiday, or outside the instrument's trading session). | Wait for the market to open. No action needed. |
NO_SL_PROVIDED | Signal missing Stop Loss | The signal did not include a stop loss, and your settings are configured to reject signals without SL. | Enable "Default SL" in Settings > Trading to provide a fallback, or change "Invalid SL Handling" to use defaults instead of rejecting. |
INVALID_VOLUME | Invalid volume | The calculated lot size is smaller than the broker's minimum (usually 0.01) or otherwise invalid. | Increase your configured lot size or account balance so that sub-order volume meets the broker minimum. |
CIRCUIT_BREAKER_OPEN | Automatic safety pause activated | Too many consecutive execution failures activated the safety pause, which pauses trading for 30 seconds. | Wait 30 seconds for the cooldown. The safety pause resets after 2 consecutive successful trades. Check Connection Issues if it keeps activating. |
Connection Errors
These errors relate to broker or Telegram connectivity.
| Code | Message | Meaning | Fix |
|---|---|---|---|
AUTH_FAILED | Broker authentication failed | Wrong login credentials, wrong server, or wrong platform (MT4 vs MT5). | Verify your credentials in Settings > Accounts. See Connection Issues. |
TELEGRAM_SESSION_EXPIRED | Telegram session invalid | Your Telegram session was terminated, either by you or by Telegram's security system. | Reconnect Telegram. Do not terminate the "TTMT Client" session in your Telegram app. |
METAAPI_DISCONNECTED | Broker disconnected | The connection to your broker's trading server was lost. | Usually resolves automatically within seconds. If persistent, check Connection Issues. |
FLOOD_WAIT | Rate limited by Telegram | Too many authentication attempts in a short period. Telegram enforces a cooldown. | Wait for the countdown timer to expire. Do not retry until it reaches zero. |
Validation Errors
These errors are caught by TTMT's safety checks before a trade is placed.
| Code | Message | Meaning | Fix |
|---|---|---|---|
SL_WRONG_SIDE | Stop loss on wrong side of entry | The SL is above entry for a BUY or below entry for a SELL, which would trigger an immediate loss. | This usually indicates a parsing error in the signal. Check "Invalid SL Handling" in Settings > Trading -- you can auto-correct, use defaults, or reject. |
SL_TOO_FAR | Stop loss distance exceeds threshold | The SL distance is more than 5x the TP1 distance, suggesting a suspicious or incorrectly parsed value. | Verify the signal is legitimate. Adjust "Extreme Value Handling" in settings if you want to allow wider stops. |
TP_WRONG_SIDE | Take profit on wrong side of entry | One or more TP levels are on the wrong side of the entry price. | Wrong-side TPs are automatically removed. If all TPs are removed, the trade may fail. Check signal quality. |
ENTRY_ZONE_INVALID | Entry zone boundaries invalid | The entry zone is inverted (low price > high price), too narrow, or too wide (exceeds 3% for forex, 5% for metals/crypto). | Usually a parsing error. Test the signal in the Signal Tester to see what was extracted. |
DUPLICATE_SIGNAL | Signal already processed | An identical signal (same symbol, direction, entry, SL, TPs) was already executed. Duplicate detection prevented double execution. | No action needed. This is a safety feature working as intended. |
MetaTrader Error Codes
These are error codes returned by the MetaTrader platform. They indicate broker-side issues.
| Code | Meaning | Fix |
|---|---|---|
10004 | Requote -- price changed during execution | Retry usually succeeds. TTMT handles this automatically. |
10006 | Request rejected by broker | Check if the instrument is available for trading and your account has permissions. |
10010 | Only partially filled | The broker could only fill part of the order. TTMT tracks partial fills and manages them. |
10013 | Invalid request | The order parameters are invalid for this broker. Check symbol specifications and volume step. |
10014 | Invalid volume | The volume does not match the broker's lot step (e.g., broker requires 0.01 increments). |
10015 | Invalid price | The requested price is outside the broker's allowed range. |
10016 | Invalid stop loss | The SL level is too close to the current price (within the broker's minimum stop level). |
10017 | Invalid take profit | The TP level is too close to the current price (within the broker's minimum stop level). |
10019 | Not enough money | Insufficient free margin to place the order. Deposit funds or reduce position size. |
10030 | Order already filled | The order was already executed. No action needed. |
Understanding Error Severity
TTMT classifies every error into one of these categories to determine whether to retry:
| Category | Behavior | Examples |
|---|---|---|
| TRANSIENT | Retried with increasing wait times | Requotes, temporary disconnects, rate limits |
| PERMANENT | Not retried, fails immediately | Invalid credentials, symbol not found |
| MARKET_CLOSED | Not retried, different handling | Weekend, holiday, outside trading hours |
| RATE_LIMITED | Retried with longer delay | Too many requests to broker |
| CONNECTION | Retried with reconnection logic | Lost connection to broker server |
Check the Signal Log
Every error is recorded in the Signal Log with full context. Click any failed signal to see the exact error code, the raw signal text, and what the parser extracted. This is the fastest way to diagnose issues.

