You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
It is the entire file for the 17th day, and on the signal line with number 1 and the rest of the lines with the number 0
I may be copying something wrong, I just am far from it google looked for this file, tell me if it is different?
Your log for the 16th endsat 11:14 p.m.
and the 17th suddenly starts at2:24 p.m.
Question: where is the record for the 17th since the beginning of the day? What happened from the beginning of the day on the 17th to14:24?
Your log for the 16th endsat 11:14 p.m.
and the 17th suddenly starts at2:24 p.m.
Question: where is the log for the 17th from the beginning of the day? What happened from the beginning of the day on the 17th to14:24?
Probably nothing happened on the terminal at 14:24 the first deal that did not open on the 17th I had nothing before that
Probably nothing happened on the terminal on vpc 14.24 the first deal that did not open I had nothing before that on the 17th
The question is, how do I know if it does not see the pair and what am I supposed to do to fix it ?
So the question is, how do you know if it can't see the pair and what should you do to fix it?
The preliminary version ( as the log is tattered and a whole chunk is missing) is that there is no space (or resources).
I don't quite understand . No space on my server or on the terminal ?
I don't quite understand . No space on my server or on the terminal ?
I've got 8GB available on the drive. The terminal is fresh and there's nothing in it.
8GB free on the drive. terminal is fresh. no indulgences anything
Yes. No disk space or the disk is virtual and occupied by another application. Why do I think so: the terminal is constantly synchronizing with the Signals service - and writes about it in the log. And you clearly have a tattered log for the 17th, i.e. the terminal was unable to log up to 14:24.
Yes. There is no disk space or the disk is virtual and occupied by another application. Why do I think so: the terminal constantly synchronises with the Signals service - and writes this in the log. And you clearly have a tattered log for the 17th, i.e. the terminal was not able to log until 14:24.
I upgraded the Windows, rebooted the server. The log seems to be fine too synchronization is fine let's hope that it will not glitch again).
Hello, everyone.
Also check that you are logged in to the Community tab.