Irrevocable proof Logfiles

New comment
 
I am in litigation with my broker for an execution error of an order, so I sent my Logfiles.

They prove many obvious errors, and this is written black and white in these "logfiles". However, they refute and do not want to reimburse me. The error was "closed market" while the market was open (impossible to close my position in the scalping session).

They claim they have nothing on their servers!

I have proof in my logfiles .. it's normal that they have nothing given that there has been a malfunction of their liquidity ..

Logfiles are irrevocable proof, how can they go in opposition to them? And is it legal?

What should I do? And answer them what?

 Logfiles are not editable, and this is the history of my account.

My broker cannot go in the opposite direction. I want to know if this is legal.

So.. where is the right place if not with Metatrader technicians and specialists??

 
Martin Lamarque:
I am in litigation with my broker for an execution error of an order, so I sent my Logfiles.

They prove many obvious errors, and this is written black and white in these "logfiles". However, they refute and do not want to reimburse me. The error was "closed market" while the market was open (impossible to close my position in the scalping session).

They claim they have nothing on their servers!

I have proof in my logfiles .. it's normal that they have nothing given that there has been a malfunction of their liquidity ..

Logfiles are irrevocable proof, how can they go in opposition to them? And is it legal?

What should I do? And answer them what?

It's not the right place to discuss such issue in my opinion. If your broker is regulated then you should contact the regulatory instance.

I doubt a log file is a "irrevocable proof" from a legal point of view, anything can be written in a log.

 
Martin Lamarque:
That's what I did. Logfiles are not editable, and this is the history of my account.

My broker cannot go in the opposite direction. I want to know if this is legal.

So.. where is the right place if not with Metatrader technicians and specialists??

Log files not editable, how is that ? A file is always editable. Anyway.

I already answered to your question, contact the regulator(s).

 
Martin Lamarque:

Do not double post.

I have deleted your other topic.

 
Martin Lamarque:
So how is it? My word (my Logfiles) against the word of the Broker? How is it that no one answers? We do not prove that this type of error necessarily comes from broker servers? 

We are not discussing the brokers here.
You should ask the broker about-

  • why they decided to close the Market for some pair in some time,
  • or for all the pairs for some day,
  • or to open the market in some hours in a day on Monday (or Sunday),
  • or to close the trading week later or earlier,
  • or to close the market during the high impacted news event,
  • or to close the Market for some official holidays for some countries which are not official hoilidays for you and for me for example,
  • and so on.

The broker's discussion is prohibited on the forum sorry.

Documentation on MQL5: Constants, Enumerations and Structures / Environment State / Symbol Properties
Documentation on MQL5: Constants, Enumerations and Structures / Environment State / Symbol Properties
  • www.mql5.com
To obtain the current market information there are several functions: SymbolInfoInteger(), SymbolInfoDouble() and SymbolInfoString(). The first parameter is the symbol name, the values of the second function parameter can be one of the identifiers of ENUM_SYMBOL_INFO_INTEGER, ENUM_SYMBOL_INFO_DOUBLE and ENUM_SYMBOL_INFO_STRING. Some symbols...
 
Martin Lamarque:
I'm not talking about the Broker! It is a rule defined for all! 

I would like to know the algorithmic process which leads MT4 to say to me "closed market": what is the information path (round trip to broker servers?; Client terminal only?; Which servers are in this process?)

It is difficult to know (if exactly).
But as far as I understand - Metatrader terminal is not a reason for this "market closing" issue.

For example, there is one thread in Russian forum where the users are talking about the following:
"why the time to execute the order is 50 ms in MT4 (for MT4 brokers) and 2-3 ms for MT5? We need nano seconds."
I have no idea why some users need nano seconds (may be - for high-frequency trading) but 1 ms = 1,000,000 nano seconds ...

So, this "market closing" issue is not coming from clients terminal programmatically.
It may be related to the broker's server  location, clients's terminal location, broker's policy, and so on ..
It is difficult to understand about it. Because it is easier to change the broker then to investigate about where this issue is coming from.
 
Martin Lamarque:

The problem in this story is that there is a lot of money at stake in this litigation, more than 6 digits lost because of these impossibilities to close the positions.

So I want to investigate and prove algorithmically speaking, that this error necessarily comes from broker servers and therefore from their responsibilities. It's the case ! But how do you prove it?

I do not know ... I think - no one can help here with reasonable advice because it is necessary to understand about "how all flow is going on" ..
 
Martin Lamarque:

It's absurd, the broker says what he wants. It's a one-way dispute in this case, MetaQuotes does not communicate on this subject, it's the same for all brokers, I don't understand why. .

Even if the broker says what he want, the broker must respond to their regulators based on the specific disservice you get (in the case that your broker is regulated of course). You should make a complaint directly to the regulators, notifying first your intention to the broker firm involved.

By the way: have you ever heard of FOS (financial ombudsman service)? Make your researchs before to post a complaint on the wrong places such as mql5.com, here you can have just some guidance.


 

Did you analyze the timestamp ?

It probably tried to close or modify orders during rollover.

New comment
Reason: