forex-scalping.com

Execution complaints usually fail because the evidence is weak: a cropped screenshot, a vague time, and a feeling that the fill was wrong. A screen recording combined with the platform's own log is much harder to dismiss.

A setup that costs nothing:

- Screen recording software (OBS Studio is free) running during the session, recording the platform with the system clock visible.
- MT4/MT5 Journal and Experts tabs, which record every order request and server response with timestamps.
- The trade history export.

When a disputed fill happens:
1. Note the ticket number and approximate time.
2. Save the recording segment from 30 seconds before to 30 seconds after.
3. Export the Journal lines for that order.
4. Put together: what you saw on screen (bid/ask at click time), what you requested, what you got, and the server timestamps.

Recordings use disk space, so many traders keep only the last few days unless something happens.

This also works the other way: sometimes the recording shows that the click came later than you remember, or that the spread really was wide. That's useful to know too.

Has anyone submitted video evidence to a broker? Did it change the outcome?

The terminal has a journal or log tab that records everything: connections, disconnections, order requests, server messages, errors. Most traders never open it.

It's a goldmine for diagnosing problems. A string of "no connection" lines at the time of a bad fill explains the delay. A "trade context busy" message points to overload. A reconnect to a different server shows a route change. Order requests with timestamps, in milliseconds on some platforms, show exactly when each message was sent and received.

When a trade went wrong, the log often has the answer, and the explanation is rarely what was assumed. Many "broker manipulation" suspicions turn out to be a brief disconnect.

For disputes, the log is also evidence. Support teams can match the entries against their server records, and a clean copy of the relevant lines makes a ticket much harder to dismiss.

Platforms rotate logs, so old files disappear. Saving the logs after any suspicious event, before they get overwritten, takes seconds.

Reading the log after each session for a week reveals the platform's normal rhythm, and anything unusual stands out afterward.

What was the most informative thing the terminal log ever revealed?