I have an issue when backtesting my bots on windows desktop version. If I perform a backtest, then change a bot parameter, it will not restart. I have to push the “pause” or “stop” buttons to make it restart. This happens since the update to 5.0.x.
I have an issue when backtesting my bots on windows desktop version. If I perform a backtest, then change a bot parameter, it will not restart. I have to push the “pause” or “stop” buttons to make it restart. This happens since the update to 5.0.x.
Hi there,
Can you please record a video demonstrating exactly what you are doing?
Wrong Account.BrokerName and Account.Number for a bot with cloud instance
Did you double-checked this? This is what I still see with v. 5.0.28:
I've also noticed that the way information is shown in the cloud cBot log/UI is not always matching the code sequence/order.
Backtesting logs: The filter (Information, Trading, Warning, Error, etc.), as well as the DateTime sort option, is still missing. Please make this available again, as it was in the previous 4.x versions.
Keep in mind that eliminating useful features can be frustrating for users. However, if there's a good reason behind this decision, please feel free to share it with the community.
Wrong Account.BrokerName and Account.Number for a bot with cloud instance
Did you double-checked this? This is what I still see with v. 5.0.28:
I've also noticed that the way information is shown in the cloud cBot log/UI is not always matching the code sequence/order.
Backtesting logs: The filter (Information, Trading, Warning, Error, etc.), as well as the DateTime sort option, is still missing. Please make this available again, as it was in the previous 4.x versions.
Keep in mind that eliminating useful features can be frustrating for users. However, if there's a good reason behind this decision, please feel free to share it with the community.
Appreciated.
Hi ncel01,
It seems that the issue is fixed in cAlgo but a fix needs to be released on the server side as well. So you will have to wait a bit more for the solution to take effect. Regarding your suggestions, please post them in the relevant section.
Wrong Account.BrokerName and Account.Number for a bot with cloud instance
Did you double-checked this? This is what I still see with v. 5.0.28:
I've also noticed that the way information is shown in the cloud cBot log/UI is not always matching the code sequence/order.
Backtesting logs: The filter (Information, Trading, Warning, Error, etc.), as well as the DateTime sort option, is still missing. Please make this available again, as it was in the previous 4.x versions.
Keep in mind that eliminating useful features can be frustrating for users. However, if there's a good reason behind this decision, please feel free to share it with the community.
Appreciated.
Hi ncel01,
It seems that the issue is fixed in cAlgo but a fix needs to be released on the server side as well. So you will have to wait a bit more for the solution to take effect. Regarding your suggestions, please post them in the relevant section.
i am not able to take any trade on FTMO account with cTrader platfarm. not able to modify and cancel my order. launched many complaints on live chat and emails but all in vain. can please guide me how can resolve my issue.
i am not able to take any trade on FTMO account with cTrader platfarm. not able to modify and cancel my order. launched many complaints on live chat and emails but all in vain. can please guide me how can resolve my issue.
We can't help you regarding this matter. You need to reach out to FTMO.
Given the absence of any clarifications, I will assume that the following has been announced by mistake:
The following issues were addressed
Wrong Account.BrokerName and Account.Number for a bot with cloud instance
Hi ncel01,
Sorry for the delay, I had to do some research for this, it seems this has not been delivered yet. It's fixed on the cAlgo side but the server team needs to do some work as well.
Given the absence of any clarifications, I will assume that the following has been announced by mistake:
The following issues were addressed
Wrong Account.BrokerName and Account.Number for a bot with cloud instance
Hi ncel01,
Sorry for the delay, I had to do some research for this, it seems this has not been delivered yet. It's fixed on the cAlgo side but the server team needs to do some work as well.
... Deleted by UFO ...