The Experts and Journal tabs are the first reliable place to investigate an EA that is silent, rejects an order or behaves differently after a VPS migration. A screenshot of the chart alone rarely shows whether the problem occurred in the strategy, terminal, account or broker layer.
Experts vs Journal
Experts mainly records messages written by Expert Advisors and indicators. Journal records broader terminal activity: connection changes, order requests, server responses, startup events and platform errors. The useful evidence is the sequence across both tabs, not one isolated line.
The same server error can have different causes. Timestamp, requested price, volume, symbol properties and the preceding messages determine the correct fix.
Common messages
| Message | What it means | Next check |
|---|---|---|
| AutoTrading disabled | The terminal or EA is not permitted to send trades | Enable AutoTrading and Allow live trading; confirm the icon and smiley |
| Invalid account / license | Server error 65 concerns an invalid trading account; a vendor license message may come from a separate activation check. | Check the message source, account and broker server; contact the broker for login problems or the vendor for its license rules. |
| Error 130 / invalid stops | SL, TP or pending price violates price or distance rules. | Check current Bid/Ask, direction, price precision and Stops Level; recalculate risk if the stop changes. |
| Error 131 / invalid volume | Lot size does not match account limits | Check minimum lot, lot step, maximum lot and free margin |
| Off quotes / requote | The requested price is unavailable or changed | Check connection, spread, market state and execution frequency |
| Trade context busy | Another trade operation is still being processed | Remove duplicate terminals or allow the EA to retry safely |
| No connection / authorization failed | The terminal cannot maintain a valid server session | Check VPS network, server selection, credentials and broker status |
Diagnostic workflow
Reproduce once without changing inputs
Note the server time, symbol, timeframe and expected action. Repeatedly changing settings destroys the evidence chain.
Read Experts around the signal
Look for the EA name, initialization result, license response, filters and the exact order parameters it attempted to use.
Match the same timestamp in Journal
Find the terminal or broker response. Record the order type, price, volume, error number and connection messages before and after it.
Classify the layer
Decide whether the issue is setup, EA logic, account permission, symbol specification, connection or broker execution.
Change one variable and retest
Apply one justified correction on Demo. If several settings are changed together, the successful fix cannot be identified.
Common diagnostic mistakes
Safe operating rule
Save the Experts and Journal files immediately after the incident, together with screenshots of EA Inputs, chart symbol and timeframe, Account History and Market Watch Specification. Remove passwords and personal information, but keep account type, server name and relevant order numbers when support needs them.
Confirm normal operation after the fix
Find the actual log files and align their clocks
Open this terminal’s Data Folder. Terminal Journal files are under logs/YYYYMMDD.LOG; EA and indicator logs are under MQL4/Logs/YYYYMMDD.LOG. The tab may display only recent messages. Its Open command opens the log folder and flushes current messages to disk.
Keep the original timestamps and record the associated time zone or server-clock offset before matching logs to orders. Normalize copies for comparison rather than editing the source evidence. An EA may not print its Inputs, request price or Magic Number automatically; request a documented diagnostic mode if those fields are needed.
Trace an uncertain request before repeating it
An illustrative sequence is: request submitted → Error 128 → connection restored → open orders and recent history reconciled → matching ticket found. In that case the original request succeeded despite the missing timely response; sending it again would be a new order. If no match is found, follow the EA’s bounded recovery procedure and retain the evidence.
Distinguish terminal connectivity from EA health and quote freshness. After a fix or restart, verify recognition of existing positions as well as disappearance of the error. Redact passwords, keys and unrelated personal data when sharing excerpts, while preserving the useful code, sequence and symbol details.
Official references describe the Journal and Experts log locations.
Turn an error into a reproducible incident
For an illustrative Error 130 incident, save more than the error line: the attempted order type, exact symbol, requested price, SL/TP, volume, contemporaneous Bid/Ask and the preceding messages. Check the relevant symbol specification and distance units. A reported Stops Level of zero does not prove that every stop distance is allowed; the server can apply dynamic restrictions.
Record which layer rejected the action and what changed in the retest. If a valid correction requires a wider stop, recalculate volume so the intended monetary risk is not silently increased. Do not treat deleting the stop or repeatedly submitting the same request as a diagnostic fix. For a timeout or uncertain response, reconcile the order pool and history before considering another request.
A useful incident note contains the EA version, time with its clock reference, one expected action, the observed response and one justified correction. Preserve the original logs and redact secrets before sharing an excerpt. The EA troubleshooting guide helps distinguish a configuration issue from an account, symbol or execution problem.