Trade Copier Not Copying? 9 Causes and How to Fix Each
Work through the nine most common reasons a trade copier stops copying, from symbol mismatch and AutoTrading to antivirus blocks and insufficient margin.

A trade opens on the provider account, but nothing appears on the receiver. Both terminals look active, and the copier was working during the previous session. A trade copier that is not working usually has a configuration, permission, account, symbol, or connection problem that can be isolated with a structured check.
The failure can occur before the provider sends the signal, while the copier processes it, or after the receiver submits the order. Identifying that stage prevents random setting changes that can create new problems.
This guide works through the nine primary causes, explains what each error means, and shows how to test every correction without risking live funds.
What Are the Most Common Reasons a Trade Copier Stops Copying Trades?
When a copier stops working, the cause is almost always one of nine things: AutoTrading disabled, symbol mismatch, insufficient margin on the receiver, lot size below broker minimum, a filter excluding the trade, terminal disconnection, antivirus interference, wrong provider or receiver assignment, or a closed market. Work through them in that order because the first checks affect the widest range of copied orders.
A complete failure means no eligible provider trades reach the receiver. A selective failure means some symbols, directions, order types, or strategies copy while others are ignored.
Copiix’s current troubleshooting guidance tells users to verify algorithmic trading, confirm that the EA is running, check the Provider and Copyer switches, inspect internet connectivity, review filters, and read the terminal logs. It also identifies symbol differences as a common reason that only some instruments fail to copy. (Source: Copiix FAQ, 2026).
| Cause | Typical symptom | First check |
|---|---|---|
| AutoTrading disabled | No receiver orders are submitted | MT4 AutoTrading or MT5 Algo Trading |
| Symbol mismatch | One instrument fails while others work | Exact provider and receiver symbol names |
| Insufficient margin | Receiver reports a funds or margin error | Free margin and calculated receiver volume |
| Invalid lot size | Trade is rejected before execution | Minimum lot, maximum lot, and volume step |
| Filter exclusion | Only certain trades are ignored | Symbol, direction, lot, Magic Number, and order type |
| Terminal disconnection | Account disappears or stops updating | Broker status and Copiix connection color |
| Antivirus interference | Console or terminal component will not launch | Quarantine and exclusion history |
| Incorrect roles | The wrong account sends or receives | Provider and Copyer assignments |
| Closed market | One symbol rejects trades at certain times | Receiver broker’s trading session |
Follow one diagnostic path at a time. Changing symbol settings, lot sizing, filters, and account roles together makes it harder to identify which correction solved the problem.
Start with a minimum-volume demo trade after every change. A successful test should confirm the symbol, direction, volume, stop levels, and closure rather than only the initial opening.
Is AutoTrading Enabled on Every Connected Terminal?
AutoTrading must be enabled on every MT4 and MT5 terminal that needs to send or execute copied trade instructions. An EA can remain visible and process data while being prevented from submitting orders.
In MT4, confirm that the AutoTrading button in the top toolbar is active. Then open Tools > Options > Expert Advisors and verify that Allow automated trading is enabled.
In MT5, confirm that the Algo Trading toolbar button is active. Open Tools > Options > Expert Advisors and check Allow Auto Trading.
MetaTrader 5 states that disabling Allow Auto Trading prevents every Expert Advisor and script from trading across the platform. Individual EA permissions cannot override the platform-wide block. (Source: MetaTrader 5 Platform Settings, 2026).
| Permission level | MT4 check | MT5 check |
|---|---|---|
| Platform-wide automation | AutoTrading button | Algo Trading button |
| Global EA permission | Tools > Options > Expert Advisors | Tools > Options > Expert Advisors |
| Chart-level permission | EA properties and Allow live trading | EA properties and automated-trading permission |
| Account-switch protection | Disable setting may turn automation off | Disable setting may turn automation off |
| Profile or chart change | Automation may be disabled automatically | Automation may be disabled automatically |
Automation can switch off after:
- Logging into another account
- Changing the active profile
- Changing the chart symbol or timeframe
- Restarting the platform after an update
- Migrating an EA to another environment
- Applying a template with different permissions
Confirm the permission on both sides. A Provider EA may detect and publish a trade while the Copyer EA is blocked from submitting the receiver order.
For cTrader, verify that the Copiix cBot instance is running. The instance should show an active state in Algo or the cBot panel rather than remaining installed but stopped.
Are the Provider and Receiver Symbols Matched Correctly?
Provider and receiver symbols must resolve to the exact instrument name used by the receiver broker. A signal for EURUSD cannot open on an account that recognizes only EURUSDm unless the suffix is configured.
A symbol is the broker-specific platform identifier for a financial instrument. Brokers can add prefixes, suffixes, dots, underscores, account labels, or entirely different market names.
Open Market Watch on both terminals and record the full symbol exactly as displayed. Do not rely on the chart title from memory.
| Provider symbol | Receiver symbol | Required correction |
|---|---|---|
EURUSD | EURUSDm | Receiver Suffix: m |
EURUSD.raw | EURUSD | Provider Suffix: .raw |
fx_EURUSD | EURUSD.pro | Provider Prefix: fx_; receiver Suffix: .pro |
DAX | GER40 | Translate: DAX:GER40 |
GOLD | XAUUSD | Translate: GOLD:XAUUSD |
US30 | Symbol unavailable | Do not copy until an equivalent contract is confirmed |
Copiix’s prefix and suffix settings use a two-stage process. The Provider removes its broker-specific characters, and the Copyer adds the characters required by the receiver broker.
A correct name does not prove that the contracts are equivalent. Compare the contract size, tick value, minimum volume, quote currency, and trading hours before mapping the instruments.
When the base names differ, configure a Translate entry instead of forcing a prefix or suffix. Copiix’s symbol translation rules support mappings such as DAX:GER30 and several comma-separated pairs.
After changing the map, open one minimum-volume demo trade. Confirm that the receiver selected the intended instrument rather than a similarly named CFD, futures contract, or account-specific variant.
Does the Receiver Account Have Enough Free Margin?
The receiver needs enough free margin to meet its broker’s requirement for the copied order. A Provider can open successfully while the Copyer rejects the same numerical lot because its leverage, equity, or existing exposure differs.
Free margin is the account equity that remains available for new positions. It is calculated after the broker reserves margin for existing positions and eligible pending orders.
MetaTrader defines free margin as equity minus used margin. The broker can also apply instrument-specific margin rules, blocked profit rules, and separate requirements for different order types. (Source: MetaTrader 5 Executing Trades, 2026).
| Margin factor | Why the receiver can differ |
|---|---|
| Lower leverage | More account funds are reserved |
| Lower equity | Less capital is available |
| Existing positions | Current margin reduces free margin |
| Pending orders | Some brokers reserve margin for them |
| Different contract size | One lot can require more margin |
| Different account currency | Margin must be converted |
| Floating losses | Equity and free margin decline |
| Broker margin multiplier | Certain symbols require additional margin |
Check the receiver’s Trade tab before testing. Record Balance, Equity, Margin, Free Margin, and Margin Level.
A receiver may have enough margin for 0.10 lot but not for 1.00 lot. Reduce the Copyer’s Fixed, Percentage, or Equity To Equity sizing rule instead of repeatedly submitting the rejected volume.
Use a margin buffer rather than consuming nearly all available funds. A position that opens at a low margin level can reach margin call quickly when spreads widen or the trade moves against the account.
Is the Copied Lot Size Valid for the Receiver Broker?
The receiver lot must fall between the broker’s minimum and maximum volume and align with its permitted volume step. An order for 0.005 lot will fail when the receiver accepts a minimum of 0.01 lot.
The Provider’s volume is only an input to the Copyer calculation. The receiver broker makes the final decision on whether the submitted volume is valid.
MetaTrader exposes SYMBOL_VOLUME_MIN, SYMBOL_VOLUME_MAX, SYMBOL_VOLUME_STEP, and SYMBOL_VOLUME_LIMIT for each instrument. A calculated lot must conform to these receiver-side properties. (Source: MQL5 Symbol Properties, 2026).
| Calculated lot | Receiver minimum | Volume step | Possible result |
|---|---|---|---|
| 0.005 | 0.01 | 0.01 | Rejected or adjusted, depending on copier logic |
| 0.01 | 0.01 | 0.01 | Valid |
| 0.125 | 0.01 | 0.01 | Must normalize to 0.12 or 0.13 |
| 1.00 | 0.10 | 0.10 | Valid |
| 5.50 | 0.01 | 0.01 | Rejected if above the maximum |
Open Market Watch > right-click the symbol > Specification in MT4 or MT5. Check the minimum volume, maximum volume, and volume step.
Review the Copyer’s money management method:
- Fixed uses a defined receiver volume or multiplier.
- Percentage scales the Provider volume.
- Equity To Equity scales according to the equity relationship.
- A Money Management Map can apply a different method to a symbol or strategy.
A very small receiver can calculate a lot below the broker minimum. The copier cannot preserve the exact proportional risk when the smallest tradable volume is already too large.
A very large Provider trade can also exceed the receiver maximum. Add a maximum-lot filter or reduce the Copyer multiplier before reconnecting the account.
Is a Copier Filter Excluding the Trade?
A copier filter can intentionally block a trade even when every terminal and broker connection is working. Review both outgoing Provider filters and incoming Copyer filters.
Filters determine which trade instructions are eligible for transmission or execution. A trade that does not match the configured condition should be ignored rather than treated as an error.
Copiix supports filters for symbols, trade direction, lot ranges, Magic Numbers, and selected trade types. Its current parameter documentation also separates Provider, Copyer, and Both modes and explains how symbol rules are applied. (Source: Copiix Parameters Configuration, 2026).
| Filter | Example setting | Trade that will be ignored |
|---|---|---|
| Symbol | EURUSD,GBPUSD | XAUUSD |
| Direction | Buy only | Sell trade |
| Minimum lot | 0.10 | 0.05-lot trade |
| Maximum lot | 1.00 | 2.00-lot trade |
| Magic Number | Include 12345 | EA using 67890 |
| Order type | Market trades only | Pending order |
| Provider ID | Provider A only | Signal from Provider B |
The section below separates basic trade filters from strategy identifiers. Check the exact field values rather than assuming an empty field always means “allow everything.”
Symbol, Direction, and Order-Type Filters
Symbol, direction, and order-type filters restrict the market activity that the copier is allowed to process.
A symbol filter can be inclusive or exclusive depending on the selected mode. Confirm whether the entered list means “copy only these symbols” or “ignore these symbols.”
Direction filters commonly distinguish Buy and Sell signals. A receiver configured for Buy only will correctly ignore a Sell even when the symbol and lot are valid.
Order-type filters can separate:
- Market orders
- Buy Limit and Sell Limit orders
- Buy Stop and Sell Stop orders
- Stop-limit orders where supported
- Pending-order modifications
- Market execution after a pending trigger
Check whether the Provider is configured to ignore pending orders until they become market positions. A pending order that is intentionally withheld is not a failed copy.
Magic Number and Comment Filters
A Magic Number identifies trades created by a particular MetaTrader Expert Advisor and can isolate one automated strategy from another.
Confirm the Magic Number on the Provider trade through the platform’s order or position details. Then compare it with the included or excluded values in the Copiix parameters.
Copiix’s current FAQ confirms Magic Number filtering but explicitly states that comments are not supported as a standard Copiix filter. Do not rely on a trade comment to select the strategy unless the specific feature being used documents that behavior.
Common Magic Number mistakes include:
- Entering the receiver Magic Number instead of the Provider value
- Selecting exclude mode instead of include mode
- Leaving an old number after changing EAs
- Assuming manually opened trades have the EA’s Magic Number
- Using different Magic Numbers across MT4 and MT5 versions
Disable one filter at a time during diagnosis. Opening every filter simultaneously can allow trades that the account was never intended to receive.
Are the Trading Terminals Connected to Their Brokers?
Both the Provider and Copyer terminals must maintain active broker connections. A local copier can transfer a signal correctly while the receiver terminal remains unable to submit it.
Check the connection indicator in the bottom-right area of MT4 or MT5. Prices should update, the account should show the correct broker server, and Market Watch should receive new quotes.
Copiix’s getting-started documentation requires the terminals to appear in the Console with platform, account, broker, and status information. It also warns that running multiple Copiix component instances inside the same platform can cause conflicts and error messages. (Source: Copiix Getting Started Documentation, 2026).
| Connection state | What it means | Action |
|---|---|---|
| Quotes update normally | Broker connection is active | Continue diagnosis |
| “No connection” | Terminal cannot reach the broker | Check internet and server login |
| “Invalid account” | Login, password, or server is wrong | Reauthorize the account |
| Prices are frozen | Feed or terminal may be disconnected | Compare broker time and last quote |
| Terminal absent from Copiix | EA or cBot is not connected | Restart the component |
| Red Copiix status | Error or disconnected state | Open the terminal logs |
| Gray Copiix status | Inactive or paused | Resume only after checking settings |
Confirm that the account is logged in with trading access. An investor or read-only password can show positions and prices but cannot submit receiver orders.
A Provider connection problem can prevent the signal from being created. A Copyer connection problem can allow the signal to arrive while the broker rejects or never receives the order.
Restart in a controlled order:
- Close the affected trading terminal.
- Confirm the Copiix Console remains active.
- Reopen the terminal.
- Confirm the correct broker account and server.
- Verify that the EA or cBot starts.
- Check the Copiix terminal status.
- Run one demo test.
Do not restart every terminal at once unless the full system has failed. Isolating one connection preserves evidence in the other logs.
Is Antivirus or Firewall Software Blocking the Copier?
Antivirus software can stop trade copying when it quarantines the Copiix Console, EA, cBot, or a required communication file. Firewall restrictions can also interfere with broker or platform connectivity.
A blocked file can produce several symptoms. The Console may fail to open, the EA may disappear from Navigator, or a terminal may never appear in the Copiix interface.
Follow the official Copiix installation guide before changing security settings. Install files only from the official Copiix website.
| Security symptom | What to inspect |
|---|---|
| Console will not launch | Antivirus quarantine and application history |
| EA missing after restart | Platform data folder and quarantined files |
| cBot cannot start | cTrader permissions and security alerts |
| Terminal never appears | Local communication component |
| Broker connection fails | Firewall rules for the trading platform |
| Problem began after an update | Newly downloaded file or changed signature |
Use the narrowest correction possible:
- Restore only the verified Copiix file from quarantine.
- Add the Copiix application folder to the antivirus exclusion list.
- Allow MT4, MT5, cTrader, and Copiix through the firewall where required.
- Restart the affected platform after restoring its component.
- Run a new scan with updated security definitions.
- Reinstall from the official package when file integrity is uncertain.
Do not disable antivirus protection permanently. A permanent system-wide exception creates more risk than a folder-specific rule for verified software.
A security product can also block writing to protected directories. Running the Console from a user-writable folder can avoid permission failures that occur inside tightly restricted system locations.
Are the Provider and Receiver Roles Assigned Correctly?
The source account must have Provider enabled, while the destination account must have Copyer enabled and connected to the intended Provider. Reversing these roles prevents the expected signal path.
A Provider broadcasts eligible trading activity. A Copyer receives instructions and applies its own symbol, money management, and filtering rules.
Copiix’s Console uses role colors and a Network Map to display account relationships. Purple identifies a Provider, green identifies a Copyer, orange identifies a dual-role terminal, red shows an error or disconnection, and gray shows an inactive or paused state. (Source: Copiix Console Overview, 2026).
| Intended account | Required role | Common mistake |
|---|---|---|
| Main strategy account | Provider | Copyer enabled only |
| Receiving account | Copyer | Provider enabled only |
| Two-way terminal | Both | Used without a clear need |
| Inactive test account | Paused | Accidentally connected to live Provider |
| New receiver | Copyer linked to Provider ID | No Provider selected |
Assign descriptive Aliases such as:
Main-MT5-ProviderPropA-MT5-CopyerBrokerB-MT4-CopyerDemo-cTrader-Test
Open the Network Map and trace the direction visually. The connection should begin at the intended Provider and end at each intended Copyer.
Check for circular relationships when Both mode is enabled. Copiix includes loop protection, but an unnecessary two-way configuration makes troubleshooting harder.
After correcting the roles, use one new test trade. An old Provider position may not be copied automatically unless the selected synchronization behavior explicitly handles existing trades.
Is the Instrument Currently Open for Trading?
The receiver broker must have an active trading session for the mapped instrument. A Provider can trade while the receiver market is closed because brokers can use different schedules.
Trading sessions are defined per symbol and per day. Forex, index CFDs, metals, stocks, futures, and cryptocurrencies can follow different hours.
MetaTrader displays quoting and trading sessions in Market Watch > Specification. The same window also shows broker-defined spread, stop levels, and margin information. (Source: MetaTrader 5 Market Watch, 2026).
| Session problem | Example |
|---|---|
| Daily maintenance break | Index or commodity pauses each day |
| Weekend closure | Forex receiver is closed |
| Holiday schedule | One broker closes earlier |
| Futures expiry | Receiver contract no longer trades |
| Stock exchange hours | Equity CFD follows exchange sessions |
| Crypto account restriction | Broker does not offer weekend trading |
| Symbol disabled | Instrument is visible but trading is not permitted |
Compare the Provider and Copyer broker times. A trade opened near the session boundary can be accepted by one broker and rejected by another.
A pending order may also be rejected outside permitted hours. Some brokers accept pending instructions while the market is closed, while others block all trade operations.
Do not repeatedly retry a market order until the session opens. A delayed entry can occur at a price and risk level that the Provider never intended.
What Do the Copier and Terminal Logs Reveal?
The logs reveal whether the trade was detected, filtered, translated, submitted, accepted, rejected, or delayed. Read them before changing the configuration.
In MT4, open the Experts and Journal tabs at the bottom of the terminal. In MT5, review Experts and Journal inside the Toolbox.
Copiix identifies the MT4 Experts log as the first diagnostic resource. Its documentation also shows connection status, terminal ID, role, active settings, trade operations, and error messages on the EA interface. (Source: Copiix MT4 Documentation, 2026).
| Log message stage | What it proves |
|---|---|
| Provider trade detected | The source component saw the event |
| Signal filtered | A configured rule blocked it |
| Canonical symbol created | Provider mapping was applied |
| Receiver signal received | Local transfer succeeded |
| Symbol not found | Receiver mapping failed |
| Invalid volume | Lot did not meet broker rules |
| Not enough money | Free margin was insufficient |
| Market closed | Trading session was inactive |
| Trade disabled | Account or symbol permission blocked execution |
| Order accepted | Broker received the request |
| Deal created | Receiver position was executed |
Capture the full message rather than only the error number. The symbol, volume, timestamp, account, and broker response provide the context needed to interpret the code.
Compare the same event across three locations:
- Provider platform log
- Copiix Console or terminal log
- Copyer platform log
This sequence identifies the failure boundary. A Provider event with no Copiix signal indicates a source-side problem, while a received signal followed by a broker error indicates a receiver-side problem.
Save a log sample before restarting the platform. Restarting or clearing the terminal can remove the easiest evidence of the original failure.
Why Are Trades Copying With Errors or Delays?
Trades can copy with errors or delays when the signal succeeds but the receiver needs extra processing, reconnects to its broker, normalizes volume, or waits for an execution response. A delayed copy is different from a missing copy.
The copied order is a new broker request. It does not inherit the Provider’s fill price or execution result.
MetaTrader 5 separates orders, deals, and positions and can use netting or hedging accounting. Trade modifications and closures must therefore target the correct receiver object after the original copy is created. (Source: MetaTrader 5 Trading Principles, 2026).
| Delay or error source | Result |
|---|---|
| Slow receiver broker connection | Later order submission or confirmation |
| High CPU or memory use | Local processing pauses |
| Symbol translation | Mapping is checked before submission |
| Volume normalization | Calculated lot is adjusted |
| Several receivers | Multiple broker requests are created |
| Fast market | Receiver fills at another price |
| Reconnection | Signal may arrive after broker access returns |
| Stop-level difference | Modification is rejected |
| Netting account | Receiver position is combined with existing exposure |
| Hedging account | Separate positions must be tracked |
A delay can also appear when the Provider and Copyer clocks are not synchronized. Compare broker-confirmed timestamps rather than relying only on the computer clock.
Monitor whether the delay affects:
- Every receiver
- One broker only
- One symbol only
- Market entries only
- Pending orders only
- Modifications and closures
- High-volatility periods
- Times of high computer load
The pattern narrows the cause. A delay affecting one broker is more likely a broker route problem, while a delay affecting every terminal suggests a local resource or copier problem.
How Do You Test Each Fix Without Risking Live Funds?
Test each correction with one Provider and one Copyer on demo accounts using the smallest valid receiver volume. Change only one setting between tests.
A real-time demo test checks current platform connections, symbol names, order permissions, and broker rules. A historical backtest cannot reproduce the complete local copier and receiver-broker route.
Copiix’s guide to real-time demo testing recommends forward testing under current conditions because historical testing cannot reproduce every execution and platform variable.
| Test | Provider action | Expected Copyer result |
|---|---|---|
| Connection | Start both terminals | Both appear online |
| Market Buy | Open minimum volume | Correct Buy appears |
| Market Sell | Open minimum volume | Correct Sell appears |
| Symbol mapping | Use a suffixed symbol | Correct receiver symbol appears |
| Lot sizing | Use a known Provider lot | Expected normalized lot appears |
| Stop loss | Add or change SL | Copyer stop updates |
| Take profit | Add or change TP | Copyer target updates |
| Pending order | Place an eligible order | Corresponding order appears |
| Partial close | Reduce Provider volume | Copyer exposure reduces |
| Full close | Close Provider trade | Copyer position closes |
| Disconnection | Stop one Copyer | Other accounts remain unaffected |
| Restart | Restart the affected terminal | Connection and roles recover |
Use this testing sequence:
- Record the original error.
- Change one suspected setting.
- Restart only when the change requires it.
- Open one minimum-volume demo trade.
- Compare all three log locations.
- Record the outcome.
- Restore filters before testing another live workflow.
Do not test a margin problem by increasing leverage or depositing funds immediately. First reduce the receiver lot and confirm that the rejection was caused by position size.
Do not use a funded prop firm account as a troubleshooting environment. Confirm the software behavior on demo, then verify that the intended copier arrangement complies with the firm’s current rules.
How Does Copiix Help Diagnose Failed Trade Copies?
Copiix helps diagnose failed copies through connection colors, terminal details, Network Map relationships, real-time execution status, latency information, and error logs. These tools show whether the problem belongs to the account, connection, configuration, or broker response.
Every detected terminal has a unique identity inside the Console. The display includes the platform, account number, broker, balance, equity, role, and current state.
Copiix has expanded its logging and error handling across recent releases, including additional log messages, MT5 permission fixes, pending-order corrections, and improved trade-opening controls. (Source: Copiix Changelog, 2026).
| Diagnostic feature | What to inspect |
|---|---|
| Terminal color | Active, paused, disconnected, or error state |
| Platform and broker | Correct account environment |
| Alias | Correct account purpose |
| Provider and Copyer role | Correct signal direction |
| Network Map | Intended account relationship |
| Execution status | Signal and order progress |
| Latency indicator | Connection degradation |
| Error log | Exact rejection or failure |
| Active parameters | Filters, mappings, and sizing |
| Balance and equity | Margin and drawdown pressure |
A trade copier error should be traced from Provider detection to Copyer execution, not guessed from the missing position alone.
Copiix runs locally across MT4, MT5, and cTrader. Its documentation describes real-time synchronization without mandatory registration and supports separate terminal roles and account configurations. (Source: Copiix Documentation: What Is Copiix?, 2026).
When requesting technical help, include:
- Copiix version
- Operating system
- Trading platform and build
- Provider and Copyer Aliases
- Broker names
- Exact symbols
- Money management method
- Relevant filters
- Full log message
- Time of the failed copy
Use the Copiix support page when the logs and documentation do not resolve the error. Remove account passwords and other sensitive credentials from screenshots or messages.
Fixing a Trade Copier That Is Not Working: Key Checks
A trade copier that is not working should be diagnosed in a fixed sequence: permissions, symbols, margin, lot validity, filters, connections, security software, account roles, sessions, and logs. This order moves from broad platform blocks to specific broker rejections.
The most useful question is not only “Why did the receiver miss the trade?” Ask where the instruction stopped.
| Diagnostic stage | Required confirmation |
|---|---|
| Provider platform | Trade event was created |
| Provider component | Event was detected |
| Provider filters | Signal was eligible |
| Local transfer | Copyer received the instruction |
| Symbol mapping | Receiver instrument was resolved |
| Money management | Receiver lot was calculated |
| Broker validation | Margin, volume, and session were valid |
| Execution | Broker accepted the order |
| Position tracking | Receiver trade remained linked |
| Closure | Final trade-management event completed |
Use this final checklist:
- Enable AutoTrading or Algo Trading.
- Confirm the EA or cBot is running.
- Match the exact broker symbols.
- Check receiver free margin.
- Verify minimum lot and volume step.
- Review Provider and Copyer filters.
- Confirm both broker connections.
- Restore any verified files blocked by antivirus.
- Check Provider and Copyer roles.
- Verify the receiver trading session.
- Read the complete error message.
- Reproduce the fix on demo.
Do not leave troubleshooting overrides active. Reapply symbol exclusions, maximum-lot rules, Magic Number filters, and prop firm restrictions after the test.
Copying losses is still copying correctly. A working copier reproduces the Provider’s trade instructions, not a guaranteed profitable result.
Restore Trade Copying With Copiix
Start with one Provider and one Copyer in a controlled demo setup, then confirm automation permissions, symbols, lot sizing, account roles, and logs before reconnecting additional accounts.
Copiix runs locally and supports MT4, MT5, and cTrader without requiring a cloud relay for the core copying process. Each Copyer can use separate symbols, filters, money management, and account settings.
Before returning to live use:
- Complete one full opening and closure test.
- Confirm stop-loss and take-profit changes.
- Review the receiver broker response.
- Restore the intended filters.
- Save the working configuration.
Once the error has been isolated and the complete copying route has passed testing, download Copiix and restore your local Provider-to-Copyer setup.
Frequently Asked Questions About Trade Copier Problems
Why does the provider show a trade that never reaches the receiver?
The signal can stop because the Provider filter excludes it, the Copyer is disconnected, or the receiver rejects the order. Compare the Provider log, Copiix log, and Copyer log in that order.
A missing receiver position does not prove that the local transfer failed. The broker may have rejected a correctly received instruction.
Can a symbol suffix stop trades from copying?
Yes, a suffix can stop copying when the receiver broker uses a name such as EURUSDm but the signal resolves only to EURUSD. Configure the receiver Suffix or a specific translation rule.
Confirm the full symbol in Market Watch. Test it on demo before applying the rule to live accounts.
Why does the receiver reject a copied lot size?
The receiver rejects a lot that falls below its minimum, exceeds its maximum, or does not align with its volume step. Insufficient free margin can create a separate rejection even when the lot format is valid.
Review the receiver’s Contract Specification and money management rule. Normalize the final lot before testing again.
Does AutoTrading need to be enabled on both accounts?
Yes, automated trading should be enabled on every MT4 or MT5 terminal that needs to send or execute copier instructions. Platform-wide and EA-level permissions must both allow trading.
Recheck the button after changing accounts, profiles, charts, or platform settings. These actions can disable automation as a protective measure.
Can antivirus software prevent a local trade copier from working?
Yes, antivirus software can prevent copying when it quarantines the Console, EA, cBot, or a required file. The affected component may fail to launch or disappear from the trading platform.
Restore only files obtained from the official source. Use a narrow folder exclusion instead of permanently disabling system protection.
Why are some trades copied while others are ignored?
Selective copying usually means that a filter, symbol mapping, order-type setting, or broker rule applies only to certain trades. Compare a successful trade with an ignored trade field by field.
Check the symbol, direction, lot, Magic Number, Provider ID, and order type. The Copyer log should identify whether the trade was excluded or rejected.
