When something goes wrong — an exchange rejects an order, a connection drops, a key fails — the terminal reports it in several places. This page describes where to look for the message, how to tell the terminal’s explanation from the exchange’s response, how to find the exchange code in the text, and what to send to support if you can’t sort it out yourself.

Codes and texts for specific exchanges are collected on separate pages — links are at the end.

Where messages appear

• Cards — pop up in the top-right corner of the window and disappear after 8 seconds. Red means a rejection or disconnect, green means success, blue means information. If the event involves an exchange, its logo appears in the line. Identical messages don’t multiply; they collapse into one card with a repeat counter.
• Alerts feed — the Alerts button in the window’s top bar. Every card is recorded there, so you can reread a message that flashed by. A blue dot on the button means there are unread items. Terminal messages live under the System source.
• Connection row in Settings → Connections. The dot color shows the connection state, and the hover tooltip gives the reason: “Exchange rejected the API key or secret”, “Disabled”, or the exchange’s last response while the connection is being re-established.
• View-only mode icon (eye) on the order book — you can’t trade from this panel right now. Hover over it: the tooltip names the reason.
• Semi-transparent orders on the order book — the terminal temporarily can’t confirm them with the exchange: the connection dropped or the exchange rate-limited requests. When the connection returns, the orders are re-verified.
• Red banner at the top of the window — Windows prevented part of the terminal from starting (Smart App Control or antivirus). It doesn’t disappear on its own. While it’s up, depending on the text, market data stops updating or orders are not sent.
• Login and update windows show their own errors directly in the window.
• Logs — the full record of the terminal’s operation, including what isn’t shown in a card. How to get them — below.

Two kinds of messages

The terminal recognizes the error and explains it itself

The terminal recognizes several common situations in any exchange’s response and shows its own text instead of the raw response — in the interface language and with a hint on what to do.

Each of these messages is broken down on the Terminal messages page.

The terminal passes the exchange response through as-is

Everything else — insufficient margin, minimum volume, price step, key permissions, IP whitelist — the terminal doesn’t translate. It shows the exchange’s text in full, usually in English. A short prefix precedes it, which tells you which action failed.

The text after the colon is the exchange’s response. Find the code in it (see the next section) and open the page for your exchange.

How to find the exchange code in the text

Every exchange has its own response format. For example, Binance responds like this:

Order: {"code":-2019,"msg":"Margin is insufficient."}

Here the code is -2019, and msg is the exchange’s explanation. Other exchanges format the code differently:

If there’s no code in the text, search by keywords: insufficient — not enough funds, timestamp or recvWindow — clock, signature — signature, permission — key permissions.

Logs and a report for support

If a message is unclear or keeps repeating, assemble a report — a single archive with all the needed logs.

The settings file with API keys and the trade journal are not included in the report. If disk space is low, the terminal says: “Not enough disk space for the report: need … MB, free … MB”.

You can also open the logs folder manually: Help → Logs. On Windows it’s %AppData%\TradingTerminal\Logs, on macOS — ~/Library/Application Support/TradingTerminal/Logs. Logs are kept for a week; older ones delete themselves.

If footprint clusters or the screener don’t load — meaning the LootX servers aren’t responding, not the exchange — open Settings → Cloud → Connection diagnostics and click Check connection. The check shows at which step the connection drops, and Copy report gives you text for support.

Error codes by exchange

Next