Trade Copier Not Working? Diagnose Signals and Order Send Errors

When a trade copier does not place an order, locate the last stage that succeeded: source event, delivery to Copygram, parsed signal, receiver routing, or broker acceptance. Then use the receiver’s exact response to investigate the failed stage. An alert firing does not prove that a trade was filled.

Reviewed on 29 September 2026. MT4 and MT5 use different return-code systems. Match the code to the actual platform, and keep the full error message when contacting support.

First, check whether the order already exists

Before retrying a timed-out or uncertain request, inspect the receiving account’s orders, positions and history. If the order is already there, another signal can create a duplicate. Record the timestamp and timezone, account, symbol, quantity and any order identifier so you can match records across systems.

Find the stage that failed

Stage	Evidence to inspect	Next check
Source	Alert log, channel message or source-account trade	Did the intended event actually occur?
Delivery	Webhook status or source connection	Was the message sent to the current connection?
Parsing	Copygram’s signal log	Were action, symbol and quantity interpreted correctly?
Routing	Room and receiver settings	Is the Room started and the receiver connected and eligible?
Acceptance	Receiver response and order history	Was the instruction rejected, accepted, pending or filled?

TradingView alert fired, but Copygram has no signal

Open TradingView’s alert log and check Webhook status. Confirm the alert uses the current Copygram webhook URL and that this connector is the source of the intended Room. Keep credentials out of the alert body. TradingView requires two-factor authentication for webhooks, accepts ports 80 and 443, and cancels a request if the destination takes longer than three seconds to respond.

These delivery requirements are documented in TradingView’s webhook guide. A delivery response still does not establish that the receiving broker accepted the trade.

Review the complete setup in the TradingView trade copier guide.

The signal arrived, but the instructions are wrong

Compare the original message with Copygram’s parsed action, symbol, size and exit instructions. Copygram accepts clear plain text or custom JSON through AI parsing, but ambiguous or incomplete messages still need correction. Remove conflicting instructions and use a supported demo account to validate the intended interpretation.

For a TradingView update or close targeting a specific trade, include a signal_id in the original alert and reuse it in the follow-up. For Telegram, an update to a specific trade should reply to the original signal. A standalone close-by-symbol instruction can have broader scope, so confirm what it will affect before using it.

The parsed signal is correct, but a receiver does not execute

Confirm the Room is started and the intended receiver is connected. Review symbol mapping, Execute Only or Avoid filters, trading schedules and the relevant entry, close or modification settings. A Room has one source; make sure the source you are checking is the one configured in that Room.

If the response mentions an unknown or unavailable instrument, use the symbol-mapping guide. Also check size increments, contract specifications, market hours, available margin and account permissions. Changing a mapping cannot fix a disabled account.

Common MT4 return codes

MT4 code	Meaning
128	The trading request timed out.
130	The stop settings are invalid.
131	The requested volume is invalid.
132	The instrument’s market is closed.
133	Trading is disabled.
134	The account lacks sufficient funds for the request.
136	A usable quote is unavailable.
138	A replacement quote was returned.
139	The order is locked.

Code meanings are checked against the official MQL4 trade-server reference. In particular, 139 is a locked order, not a timeout; timeout is 128.

MT5 codes are different

In MT5, examples include 10012 for a timeout, 10014 for invalid volume, 10016 for invalid stops, 10017 for disabled trading, 10018 for a closed market and 10021 when no quotes are available to process the request. Do not interpret these using the MT4 number list.

Use the official MQL5 trade-server reference for the exact return code and description.

Use the error to choose the next check

For invalid stops, compare the receiver’s current price, order direction and instrument rules with the requested SL/TP. Do not blindly widen or remove stops to make an order pass. For invalid volume, compare the final receiver quantity with its minimum and step size, including any Copygram Symbol Lot Exception.

For unavailable quotes or a closed market, inspect the receiver’s quote feed and instrument session. For disabled trading, check the account and broker permissions. Repeated retries, a larger slippage setting or restarting a local terminal do not resolve every cause; Copygram’s hosted connections do not require a local VPS for the Room.

What to send Copygram support

• The Room and affected receiver, plus a timestamp with timezone.
• The source platform and a redacted copy of the alert or signal.
• The parsed action, source symbol, mapped destination and final quantity.
• The exact receiver error, relevant settings and order identifier when available.
• Whether the receiving account already shows an order or position. Remove passwords, webhook secrets and unnecessary personal information.

Check the current Copygram documentation or use the website’s contact page for help.

Build a route you can verify

For MT4 and MT5 receivers, start with the MetaTrader trade copier guide.

For TradeLocker receivers, review the TradeLocker setup guide. TradeLocker cannot currently act as a Copygram source.

Compare Copygram’s current plans once you have confirmed the source features, connected accounts and permissions your setup requires. Copygram does not offer a free trial.