Troubleshooting: when a signal doesn't trade

Start with the audit trail, not a retype

Every signal's journey is recorded from admission to queueing to EA delivery to the broker's result, so do not retype anything by hand. A signal sitting review-only arrived before routing was enabled, failed to parse, or is a duplicate. A refused or expired command names whether the mapping, the licence, the terminal session, or the freshness window stopped it.

The usual causes are ordinary configuration: the provider's symbol has no mapping to your broker's symbol yet, the stop sits on the wrong side of the market or inside the minimum stop distance, the terminal session lapsed, or the licence stopped allowing new entries. Fix the cause, then let the next new signal prove it.

If the EA never connects

Check the terminal first: it must be running, Algo Trading (MT5) or AutoTrading (MT4) enabled, and the EA attached to a chart — on MT4 that attach is manual. If MetaTrader never whitelisted the loopback URL, the EA falls back to its file channel on its own; only the MT5 WebRequest permission error (4014) needs you to add the URL under Tools, Options, Expert Advisors.

On the app side, the Diagnostics page shows bridge state and connected terminals. A terminal that shows connected but produces no trades means routing is disabled or unconfigured — check the gate, not the connection.

If the broker rejects the order

A rejection carries the broker's own result code plus a category. Retried automatically is never one of them: a retryable outcome means a fresh command may be reasonable after you check price and state, while uncertain outcomes must be reconciled in the terminal before anything new is sent.

Common verdicts are trading disabled in the terminal, a closed market, insufficient margin, or a broker limit reached. Each arrives as a readable reason rather than a bare code.

If the dashboard shows no trades

The dashboard mirrors results, snapshots, and journal notes synced from the device — message content never leaves your PC. If the terminal traded but the dashboard is empty, the sync drain is behind: check Diagnostics for outbox activity and confirm the machine has been online. The machine running the app must stay on throughout; a Windows VPS counts as one of your three paired devices.

What never to share

When asking support for help, include your account email, the device name, what you expected, and the broker response code if there is one. Never share login codes, two-step passwords, API hashes, QR links, session files, or private message logs — support never needs them and you should never send them.