Skip to main content
Help›Knowledge base›Error Messages
Error Messages

"Unknown symbol" — what to change

The instrument name in the signal does not exist at your broker.

The signal named an instrument your broker does not carry under that name. PipSync refuses rather than guessing at a similar one, and no order is placed. The signal shows as rejected, and in Trading Hub → Execution Log (open the signal's row) the account's error reads EXACT_BROKER_SYMBOL_NOT_FOUND, often followed by the names PipSync tried, or Failed to select symbol … on MT5.

Fix it

  1. Open Market Watch in your terminal and show all symbols, not the default list.
  2. Find the real spelling. It is often suffixed: XAUUSD.raw, EURUSD.m, US30.cash.
  3. Add a mapping on the channel so the signal's name is translated: Channels → your channel → Settings tab → Auto-trade panel → Symbol mapping, then Save mapping:
GOLD   -> XAUUSD.raw
NAS100 -> USTEC

The mapping applies to the accounts the channel trades on through the Trade Gateway and to MetaTrader accounts connected directly; Interactive Brokers accounts and older direct Match-Trader connections keep their own names. If the channel trades at several brokers that spell the instrument differently, message us in the support chat with the symbol, the exact name at each broker, your broker and your MT5 server name, and PipSync can add a symbol override for that broker.

Symbol mapping is available on every plan.

Then check the size

A suffixed variant is a different symbol with a different contract size — often a tenth. After you map a symbol, check the lot size of the next trade on it (the volume under Open Positions on the account page) before assuming you are done.

When there is no equivalent

Some brokers simply do not offer the instrument. Add it to the channel's Blocked symbols (Channels → your channel → Settings tab → Auto-trade panel → Signal filters). Its signals are then saved as rejected with the reason "on the channel's blocked symbols" and never sent to your broker, instead of each one failing there with this error.

Related: Symbol names and broker suffixes.

Was this helpful?

Still stuck?

Open a ticket and we will pick it up from your account context.