Reading the platform journal: where the real error messages live
Posted: Sat Oct 31, 2026 8:26 pm
Platforms keep logs that most traders never open. The journal and experts tabs in MetaTrader hold a detailed record of connections, orders, errors and script messages.
Typical entries include connection lost and restored, order sent, order rejected with an error code, requotes, invalid stops and trade context busy. Timestamps show how long each step took.
Reading the journal after a bad fill or a strange event often explains it. A gap in connection, a reject followed by a retry, or a delay between sending and confirmation can be seen directly.
Saving the logs before they rotate keeps history for later analysis. The files sit in the platform's data folder and can be loaded into a spreadsheet.
Patterns appear. A certain error code that keeps appearing around the same time each day suggests a systematic issue, like a server restart or a lag spike.
Support teams also respond better when sent the exact lines from the log than when given a vague description.
What have you discovered by reading your platform logs?
Typical entries include connection lost and restored, order sent, order rejected with an error code, requotes, invalid stops and trade context busy. Timestamps show how long each step took.
Reading the journal after a bad fill or a strange event often explains it. A gap in connection, a reject followed by a retry, or a delay between sending and confirmation can be seen directly.
Saving the logs before they rotate keeps history for later analysis. The files sit in the platform's data folder and can be loaded into a spreadsheet.
Patterns appear. A certain error code that keeps appearing around the same time each day suggests a systematic issue, like a server restart or a lag spike.
Support teams also respond better when sent the exact lines from the log than when given a vague description.
What have you discovered by reading your platform logs?