To verify a copied trade in under a minute, open the copier’s log, find the entry matching your trade’s timestamp, then cross-check it against the MetaTrader terminal’s Experts and Journal tabs using the same timestamp and order ID. Three outcomes tell you everything: the copier logged success, the terminal accepted the order, or the broker returned a rejection code. That three-way match is the fastest diagnostic you have.
Quick triage (60 seconds):
- Step 1: Open the Local Trade Copier log and locate the entry for the trade in question.
- Step 2: Open the MT4/MT5 terminal, switch to the Experts tab (EA behavior) and Journal tab (execution events).
- Step 3: Match the timestamp and order ID across all three. A mismatch or error code in any one of them tells you exactly where the chain broke.
Key Takeaways
Monitoring copier logs means matching the copier’s own log entry against the MetaTrader Experts and Journal files using the same timestamp and order ID — that three-way check identifies whether the copier, the EA, or the broker is responsible for any failure.
| Point | Details |
|---|---|
| Three-way log match | Cross-check copier log, Experts tab, and Journal tab using the same timestamp and order ID. |
| Files on disk beat the UI | Terminal tabs truncate; open dated .log files in MQL4/MQL5/Logs with Notepad++ or VS Code for full history. |
| Error codes route your support ticket | Broker error codes (134, 130, 135) go to the broker; EA runtime errors go to copier support. |
| Export checklist for support | Include copier log, Experts log, Journal log, EA settings screenshot, and a timeline summary. |
| Mt4copier | Writes a timestamped log for every copy event across MT4, MT5, and DXTrade with a 7-day free trial. |
Where do you find copier and MetaTrader logs?
MetaTrader’s documentation draws a clear line between two log types: the Experts tab records EA behavior, Print() output, and copier actions; the Journal tab records platform-level events like order execution, connection status, and server responses. The terminal UI shows both, but it truncates older entries. For full history, you need the files on disk.
Terminal UI locations:
- MT4/MT5: bottom panel → Experts tab (EA/copier output) and Journal tab (execution/server)
- DXTrade: check the platform’s built-in activity log or the copier’s own log window
Filesystem paths (Windows/VPS):
- MT4 EA logs:
%APPDATA%MetaQuotesTerminal[InstanceID]MQL4LogsYYYYMMDD.log - MT5 EA logs:
%APPDATA%MetaQuotesTerminal[InstanceID]MQL5LogsYYYYMMDD.log - MT4/MT5 Journal:
%APPDATA%MetaQuotesTerminal[InstanceID]LogsYYYYMMDD.log - Local Trade Copier log: written to the EA’s own log file in the MQL4/MQL5 Logs folder for the terminal it runs on
To open these, go to File → Open Data Folder inside the terminal, then navigate to MQL4/Logs or MQL5/Logs. Open the dated .log file in Notepad++ or VS Code for full, untruncated history. The terminal UI is fine for a quick glance; the files on disk are what you need for real troubleshooting, as EA debugging guidance from FXVPS confirms.
Pro Tip: On a Windows VPS running multiple terminals, each instance gets its own folder named by a unique hash (the InstanceID). Before opening logs, confirm you’re in the right instance folder — wrong folder, wrong logs.
For setup confirmation, the Local Trade Copier installation guide shows exactly which terminal the EA should be attached to, which helps you identify the correct instance folder from the start.
How to read a copied order’s log entries
Every copied trade leaves a traceable chain across three sources. MT5 log analysis guidance describes the flow as: send → check → execute → result. Read logs in that sequence, not in isolation.
Fields to match across all three sources:
- Timestamp (to the second)
- Master account ID and client account ID
- Instrument (symbol name, exact spelling)
- Direction (buy/sell)
- Volume (lots)
- Original order ID (master) and copied order ID (client)
- Execution result or error code
Annotated examples:
Successful copy (Experts log):
2026.03.14 09:31:02 LocalTradeCopier: Copied BUY 0.10 EURUSD from #12345 to #67890 [OK]
Broker rejection (Journal log):
2026.03.14 09:31:03 #67890: OrderSend error 134 (not enough money)
EA parameter error (Experts log):
2026.03.14 09:31:02 LocalTradeCopier: Invalid volume 0.00 for EURUSD — lot step mismatch
Copier helpdesk documentation shows real examples where a -1.0 style error in the copier log points to EA misinterpretation, not a broker rejection. Knowing the difference saves you from contacting the wrong support team.
Common error codes and what they mean:
- 134 — Not enough money (balance/margin issue on client account)
- 130 — Invalid stops (SL/TP outside broker’s minimum distance)
- 135 — Price changed / off quotes (requote during execution)
- 148 — Trade context busy (another order being processed)
- 4107 — Invalid volume (lot size below minimum or wrong step)
Pro Tip: Always read the two lines before and after an error. The surrounding context usually shows whether the copier sent a valid instruction and the broker refused it, or whether the EA never sent the order at all.
Step-by-step troubleshooting checklist
Work through this in order. The fastest fixes come first.
- Confirm the copier is enabled. Check that the Local Trade Copier EA is running (smiley face icon on the chart, not a sad face) and that AutoTrading is on.
- Verify master/client mapping. Open EA settings and confirm the master account number matches what’s in the copier config. A single transposed digit stops all copying.
- Check symbol name matching. Some brokers append suffixes (EURUSD.m, EURUSD_i). The copier’s symbol map must match the client broker’s exact symbol name.
- Confirm lot step and minimum. If the master trades 0.01 lots but the client broker’s minimum is 0.10, the copy fails with error 4107.
- Check the Journal for broker rejection codes. If the copier logged “sent” but no order appeared on the client account, the Journal will show the broker’s error code.
- Check the Experts log for EA runtime errors. Missing Print() output means the EA may have crashed or been detached from the chart.
- Verify account balance, leverage, and trading hours. Insufficient margin, a closed market, or a weekend trading restriction all produce silent failures.
- Run a test trade. Place a known small trade (0.01 lots, EURUSD) on the master account and watch both the Experts and Journal tabs in real time. You should see the copier log the action and the Journal confirm execution within half a second.
For a deeper walkthrough, the Local Trade Copier troubleshooting page covers the most common failure modes with product-specific steps. If you’re seeing error 133 specifically, there’s a dedicated error 133 guide that walks through the exact fix.
Before contacting support, collect: the exact timestamp of the failed trade, the Experts log slice covering that minute, the Journal log slice for the same window, and a screenshot of your EA settings.
How to collect and export logs for support
Sending the right files the first time cuts resolution time significantly. A dedicated Log tab provides a chronological action history with precise timestamps, which is exactly what support needs to trace what happened.
Files to include:
- Local Trade Copier log file (YYYYMMDD.log from MQL4/MQL5/Logs)
- Terminal Experts log (same date range as the incident)
- Terminal Journal log (same date range)
- Screenshot of EA settings panel
- Screenshot of the Accounts list showing master/client mapping
Export steps:
- In the terminal, go to File → Open Data Folder.
- Navigate to
MQL4/Logs(orMQL5/Logs) and copy the relevant dated.logfiles. - Navigate to
Logs(one level up from MQL4/MQL5) for the Journal files. - Open each file in a text editor, verify it’s readable, and save as UTF-8.
- Zip all files together with a clear filename:
SupportRequest_YYYYMMDD_AccountID.zip.
Timeline template to include in your support message:
09:30:45 — Master trade opened on account #12345 (BUY 0.10 EURUSD)
09:30:46 — Expected copy on client account #67890
09:30:46 — Copier log shows: [paste the exact line] 09:30:46 — Journal shows: [paste the exact line]
What to redact vs. keep:
- Redact: passwords, API keys, personal identification
- Keep: timestamps, order IDs, account numbers (needed to trace the event), error codes
Copier dashboards typically log timestamp, signal type, source and target accounts, instrument, volume, execution result, and error details — include all of these in your export.
Best practices for reliable copier log monitoring
A few configuration habits make the difference between a five-minute diagnosis and a two-day support thread.
- Enable verbose/debug mode only when troubleshooting. Leaving it on permanently bloats log files and makes it harder to find relevant entries.
- Keep 30–90 days of logs on your VPS. Active multi-account setups generate enough volume that older logs get overwritten or truncated. Schedule a daily zip-and-archive task using Windows Task Scheduler.
- Never store logs in shared or public folders. Log files contain account IDs and order history. Keep them in a private directory with restricted access.
- Run terminals on a dedicated Windows VPS when managing more than two accounts. Local machines sleep, restart, and lose connectivity. A VPS stays up. The VPS and security guide covers the right setup for running the copier reliably around the clock.
- Don’t rely on the terminal UI alone. The Experts and Journal tabs truncate. The files on disk are the authoritative record.
Pro Tip: On a VPS, set up a simple batch script that copies the previous day’s log files to a dated archive folder each morning. You’ll never lose a log to rotation again, and you’ll always have a clean file ready for support.
For prop-firm traders, the recent safety improvements in Local Trade Copier include monitoring enhancements worth reviewing if you’re running funded accounts.
Is the issue the copier, the broker, or the platform?
Use this decision path before opening any support ticket.
If the copier log shows “sent” but no order appears on the client account:
Check the Journal for a broker error code (134, 130, 135, etc.). That’s a broker-side rejection. Contact your broker with the Journal log slice and the exact error code.
If the Experts log shows an EA runtime error or no Print() output at all:
The EA may have crashed, been detached, or hit a parameter conflict. Contact Local Trade Copier support with the Experts log and your EA settings screenshot.
If the Journal shows repeated connection or authentication events:
The terminal lost its connection to the broker server. Investigate your VPS network stability or broker server status first.
Template for broker support:
Template for copier support:
Collect both sides of the evidence before opening either ticket. Support teams on both sides will ask for the same files, and having them ready avoids the back-and-forth that stretches a simple fix into days. For algo trading in MT5, the same log-tracing discipline applies whether you’re debugging a copier or a standalone EA.
Why local logs are the only source you can fully trust
The terminal UI is convenient, but it’s not reliable for serious troubleshooting. Entries scroll off, timestamps compress, and you can’t search across a session. The raw .log files on disk don’t have those limits. Every event is there, in order, with millisecond precision.
Account managers who’ve run multi-account setups for any length of time develop a habit: before assuming a strategy misfired or a market moved against a position, they pull the log files first. Nine times out of ten, the answer is in the Experts or Journal log within two minutes. A broker rejection code, a lot-step mismatch, a symbol suffix error — these are all fixable in minutes once you can see them clearly.
The distinction between the terminal UI and the files on disk isn’t a technical footnote. It’s the difference between guessing and knowing. Gather logs before drawing any conclusions about execution quality or strategy performance. Past results do not guarantee future performance.
Mt4copier gives you faster access to the logs that matter
Mt4copier’s Local Trade Copier writes a detailed, timestamped log for every copy event — including the master account source, client account target, instrument, volume, execution result, and any error codes. You get a filterable history that maps directly to the MetaTrader Experts and Journal files, so cross-referencing takes seconds rather than minutes.
The demo video shows exactly where the Logs tab appears in the UI and how to read a copy event end-to-end. For installation and EA placement, the setup guide walks through every step for MT4, MT5, and DXTrade. When you’re ready to run it on a VPS for 24/7 uptime, start with the security and VPS guide to get the configuration right from day one. Mt4copier has been the go-to locally-installed copier for MT4, MT5, and DXTrade since 2010, with 3,000+ active users and a 7-day free trial to get started.
Sources
- Monitoring — mytradr Docs
- TC – 4.1.7. Log Tab — ETP
- MT5 Log Analysis: How to Find EA Errors, Execution Issues, and Order Problems – トリロジー金融メディア
- Common EA Failures & How to Debug Them | FXVPS
Recommended
- Local Trade Copier DEMO on MT4 and MT5
- Local Trade Copier installation on MT4 (old version)
- How to Use MT4 to DxTrade Copier User Manual | Trade Copier for MT4 & MT5
