It uses your cBot's timezone. If there isn't one set, it's UTC+0
Well, that's annoying. According to the way it's implemented, if I wanted any cBot to log in local time for the time zones I go through because I travel often, I would have to update, recompile, and redeploy the bot every single time I cross a timezone to update the bot instances with the timezone I'm in?
Who decided that?! O.M.G. face palm
cTrader can certainly determine if the cBot is running locally (and not in the cloud), and can also determine if there's a timezone set or not.
If I start a cBot on a VPS that's set for my local time zone running an instance of cTrader bot locally (not in the cloud) set to the current timezone I want to use, then why doesn't the bot, by default if no time zone is specified and it's running locally, use the local time zone?!
It makes more sense to use the timezone the user has selected in cTrader in than a default UTC+0.
This is not something that works out of the box, automatic timezone detection needs to be developed. Feel free to post a suggestion in the Suggestions and we will consider it for future releases.
This is a known issue in cTrader 4.8 and should have been resolved in v5.0. Can you please download v5.0 and let me know if the issue persists?
https://ctrader.com/download
Best regards,
Hello,
I just uninstalled the previous version and installed the new version 5.0.21
I am afraid that the problem persists and with the same messages in the logs.
Attentively,
Pedro
Hi there,
Could you please share some screenshots with the log messages andsend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
Best regards,
cTrader Team
Hi Pedro,
This does not look like 5.0.21. Can you please share a full screenshot of the UI?
Best regards,
Panagiotis
Thank you, we are looking at it. In the meanwhile try giving full access permissions to your strategy
Are you saying that the TradeResult is a Task type?
Also, regarding the Stop() method behaviour. It's not listed as Async even though it behaves as such.
Cheers,
Clark
Hi Clark,
Are you saying that the TradeResult is a Task type?
TradeResult is a type on its own
Also, regarding the Stop() method behaviour. It's not listed as Async even though it behaves as such.
It's not Async, the execution is stopped after the calling method has been executed too. If you don't want to execute the code after the Stop() method, you need to rethink your implementation.
Thank you for reporting this issue. Could you pleasesend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
PanagiotisCharalampous
28 May 2024, 11:41
RE: RE: cTrader v5 .Algo File does not overwrite
RiskOnTrade said:
We managed to reproduce the problem and we will fix it soon
@PanagiotisCharalampous