Closed superhero closed 1 month ago
I also encountered identical issue around 2 months ago and created a support ticket. Haven't been able to resolve it and ticket got closed. Just got back to check new version release and I'm seeing this is still ongoing.
This is also blocker for my implementation, and paying for the service is not a problem. Even though I don't need more than 2 accounts.
The error above happens when the connection to the broker is lost. It is OK if it happens for a short period of time and rarely as the uptime of the broker connection in the MT terminal itself is not perfect both for MT4 and MT5 platforms. If it happens frequently or for prolonged periods of time for your trading account we recommend you to contact support to check if uptime of your trading account can be improved.
I'll be closing this ticket as this is not a bug in the SDK itself.
This is a bug with metaapi, or a required feature request with the sdk, depending on how you see it... I would classify it as a bug as there is no such issues when I set up my own infrastructure, and the timeouts can not be caught and handled by the developer... Instead the output is spammed to the stdout to an extent that it's unusable.
If you do not reopen this and fix the problem, then I will also stop working with the solution you offering and simply work with my own infrastructure solution, as this is clearly a problem with the sdk that metaapi should solve for anyone to be able to work with the sdk.
No matter if this problem is resolved by talking to the broker or any other support, it doesn't change the fact that we as developers need to be able to handle the timeouts, or any other error message from the server.
I have the same error as stated in ticket #2 , and my account is deployed and connected... I know so, because the timeout shows sporadically. Meaning, sometimes it's a timeout, sometimes it's not.
I could more or less ignore the timeout error I think, and it would work just fine, however... the error message eats up the whole log, so it's impossible to follow what's going on.
idk if it's a bug a feature request or documentation request, if so, then; how to catch these timeouts and log them according to once own preference?
...or better yet, how can I solve the problem with sporadic timeouts. Currently I'm testing this on ftmo demo server through your london gateway. Maybe it's a common problem because it's their demo server?
Code example:
and output:
And then the message is repeated:
In between these timeouts, I'm still able to read the price changes, and open and close positions, perhaps there is some gap I fail to notice, but looks to me like it works.
if it's a matter of paying for the service to solve the issue, that's not an issue, I do expect to pay to have more than 2 accounts in the future. I'm currently just testing the integration, which I am impressed with, apart from above stated problem....