Start with the strategy state
Open Copy strategies and find the affected route. A strategy must show Running before it can process new source events. Stopped means the configuration is saved but new source trades are not being copied.
If the runtime state is unavailable, refresh before changing the configuration. Do not infer a running state from the fact that the strategy exists.
Read each account state literally
Open MT5 accounts and refresh the source and affected followers. TradeMirror distinguishes live MT5 data from a cached fallback. Cached values are useful context, but they do not prove that the account is connected now.
For a new connection, enter the broker-provided MT5 server name or URL exactly as supplied. ConnectX does not require a broker search or a separate IP field.
Use the visible state and recovery action
| Visible state | Meaning | Next action |
|---|---|---|
| Stopped | The strategy configuration exists, but new source events are not being copied. | Review the route and sizing, then start it only if the configuration is correct. |
| Runtime unavailable | TradeMirror could not confirm the current strategy service state. | Refresh the strategy data. Do not assume the route is running. |
| Cached data | The account view is showing the most recently saved MT5 snapshot. | Use Refresh now and check whether live MT5 data becomes available. |
| Failed or unconfirmed | An execution receipt needs attention; it is not proof of the final broker state. | Check the follower directly in MT5 before considering any retry or manual action. |
Check whether the source event is supported
TradeMirror handles trade opens, closes, stop-loss changes, and take-profit changes. Confirm that the source event occurred after the strategy entered its running state and that the intended source account produced it.
Check follower sizing and broker constraints
Recalculate the requested follower volume from the saved lot multiplier or fixed-lot value. Then check the follower's symbol, minimum and maximum volume, lot step, available margin, account mode, and trading availability.
A correct TradeMirror calculation can still be rejected by an MT5 broker. Review the sizing guide for worked examples and limitations.
Review receipts and alerts without overreading them
Strategy details can show available execution receipts, including failed or unconfirmed instructions. Settings can show operational alerts for execution, connectivity, and configured risk events. These records help identify what needs attention, but they do not replace the actual follower account in MT5.
An ambiguous response can leave TradeMirror unable to confirm a broker result. Verify whether the follower position already exists before using a guarded retry or taking manual broker action.
Recovery order
- Stop the affected strategy if its state is uncertain.
- Check the source and follower accounts directly in MT5.
- Refresh TradeMirror account and strategy data.
- Confirm the server, roles, sizing method, and saved value.
- Review available receipts and operational alerts.
- Restart only after the route matches your intention.
If you still cannot identify the cause, email support@trademirror.io with the strategy name, affected follower label, event type, and time. Never send an MT5 password, API token, or refresh token.
Prevent the next avoidable issue
Use the pre-flight checklist before restarting and read the trade-copying risk disclosure.