Troubleshooting
Answers to the most common issues — trades not copying, copy failures, group deactivation, and what your notifications mean.
Trades aren't being copied
Work through this checklist from top to bottom. Most issues are resolved by the first three checks.
ℹ️ Note
“Failed Copies” counter on the dashboard
The Copies Today card on the Dashboard shows two numbers: successful copies and failed copies. If the failed count is greater than zero, click the red number to expand a detailed list showing exactly which trades failed, on which follower accounts, and why.
The most common reasons a broker rejects a copied order are:
ℹ️ Note
Group was auto-deactivated after a breach
If the leader account hits a risk limit (daily loss, max drawdown, etc.), SyncMyTrade automatically deactivates the entire group to protect all follower accounts. When this happens, a persistent red banner appears at the top of the Dashboard:
Leader account “Apex-Master” was breached. Group has been deactivated. Please change the leader and reactivate the group.
To recover:
Go to the group settings (click the group name on the Groups page).
Remove the breached account from the leader role.
Assign a different account as the new leader, or leave the group without a leader for now.
Save the changes and re-activate the group.
⚠️ Important
“Contract is not mapped” notification
You may see a notification like:
Contract “XYZH6” is not mapped. Please select a valid contract from the dashboard to enable trade copying.
This means your leader traded a contract that is not in SyncMyTrade's supported contracts list. This is a platform-level limitation — it is not something you can fix by adding the contract on your dashboard.
Here is exactly what happens under the hood when your leader places a trade:
⚠️ Important
Rate limit dot is yellow or red
On the Dashboard, each connection (leader and followers) shows a small coloured dot. This dot indicates how close the connection is to the broker's API rate limit — the maximum number of requests SyncMyTrade can make to that broker per minute.
Green — Under 60% of API limit used — all good, no action needed.
Yellow — 60–85% of API limit used — elevated usage. This can happen when many orders are placed or modified rapidly. Usually resolves on its own.
Red — Over 85% of API limit used — high risk of order delays. If trades are missing or slow, this may be the cause. Avoid placing a large number of orders in quick succession.
💡 Tip
Understanding notifications
The bell icon in the top navigation shows real-time events from the last 24 hours. Here is what each notification type means and what to do about it.
A trade was copied to at least one follower account but the broker rejected the order.
What to do: Click the red Failed Copies number on the Dashboard to see which accounts were affected and the broker's rejection reason.
A broker connection went offline — the OAuth token expired (Tradovate) or the API key was revoked (ProjectX).
What to do: Go to Connections and reconnect the affected connection. See the Brokers & Connections article for steps.
A previously disconnected broker connection has come back online successfully.
What to do: No action needed. Copying will resume automatically.
A trading account hit a risk limit — daily loss, max drawdown, or a platform-level rule. The account status changes to Breached.
What to do: If this is the leader account, the group will also be deactivated. See the section above on recovering from an auto-deactivated group.
A copy group was activated — either by you manually, or automatically after setup completed.
What to do: No action needed. The group is now live and copying trades.
A copy group was deactivated — either by you manually, or automatically due to a leader breach.
What to do: If you did not deactivate the group yourself, check for an account_breach notification and follow the recovery steps above.
ℹ️ Note
Still not resolved?
If you've gone through this guide and the issue persists, reach out to support. Include as much detail as possible — the group name, broker, the time the issue occurred, and any notification messages you saw.
Contact Support
We typically respond within a few hours.
Was this article helpful?