Easiest solution is it you're running your bots in the cloud - don't. You have no control over them nor the server like you do on your own vps. You also have no idea the maintenance schedule and when they might be stopping cloud instances.
Thanks. I will give that a try. Do you have any recommendations? I am running 10 cBots and would like low latency. Was looking into BeeksFX, but not really sure what to look for.
Easiest solution is it you're running your bots in the cloud - don't. You have no control over them nor the server like you do on your own vps. You also have no idea the maintenance schedule and when they might be stopping cloud instances.
Thanks. I will give that a try. Do you have any recommendations? I am running 10 cBots and would like low latency. Was looking into BeeksFX, but not really sure what to look for.
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
I did a check with backtesting, and the bot definitely misses trades. One position from last week was not taken and closed, and another one at the end of the week was not opened. See the screenshot of the trades that were taken in the backtest, but not with my bot running.
Unfortunately I cannot help you with such information. You need to follow my advise in my previous post. Add logs to your cBot to understand what happens in real time execution. Also compare it with execution on a VPS
Hello. I came across the same problem this morning. I think it is due to incorrect value of the MACD. See attached images.
MACD is the leading indicator to close positions. At 06:00 the MACD flipped negative, meaning that the position should be closed. But the value is not printed as negative, but as a formula: -8.282095762690567E-05. At 10:00 am the MACD is printed as -0,0001373403922979577 and the position is closed.
Can you look into this?
Thanks,
Vince
Any ideas? Is it possible to stop the formula results but calculate the MACD as a absolute value?
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
I did a check with backtesting, and the bot definitely misses trades. One position from last week was not taken and closed, and another one at the end of the week was not opened. See the screenshot of the trades that were taken in the backtest, but not with my bot running.
Unfortunately I cannot help you with such information. You need to follow my advise in my previous post. Add logs to your cBot to understand what happens in real time execution. Also compare it with execution on a VPS
Hello. I came across the same problem this morning. I think it is due to incorrect value of the MACD. See attached images.
MACD is the leading indicator to close positions. At 06:00 the MACD flipped negative, meaning that the position should be closed. But the value is not printed as negative, but as a formula: -8.282095762690567E-05. At 10:00 am the MACD is printed as -0,0001373403922979577 and the position is closed.
Can you look into this?
Thanks,
Vince
Any ideas? Is it possible to stop the formula results but calculate the MACD as a absolute value?
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
I did a check with backtesting, and the bot definitely misses trades. One position from last week was not taken and closed, and another one at the end of the week was not opened. See the screenshot of the trades that were taken in the backtest, but not with my bot running.
Unfortunately I cannot help you with such information. You need to follow my advise in my previous post. Add logs to your cBot to understand what happens in real time execution. Also compare it with execution on a VPS
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
I did a check with backtesting, and the bot definitely misses trades. One position from last week was not taken and closed, and another one at the end of the week was not opened. See the screenshot of the trades that were taken in the backtest, but not with my bot running.
Unfortunately I cannot help you with such information. You need to follow my advise in my previous post. Add logs to your cBot to understand what happens in real time execution. Also compare it with execution on a VPS
Hello. I came across the same problem this morning. I think it is due to incorrect value of the MACD. See attached images.
MACD is the leading indicator to close positions. At 06:00 the MACD flipped negative, meaning that the position should be closed. But the value is not printed as negative, but as a formula: -8.282095762690567E-05. At 10:00 am the MACD is printed as -0,0001373403922979577 and the position is closed.
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
I did a check with backtesting, and the bot definitely misses trades. One position from last week was not taken and closed, and another one at the end of the week was not opened. See the screenshot of the trades that were taken in the backtest, but not with my bot running.
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
vince.stans
14 Feb 2025, 20:46
RE: cBot restarts automatically - reset of cBot, resulting in incorrect bot behavior
firemyst said:
Thanks. I will give that a try.
Do you have any recommendations? I am running 10 cBots and would like low latency. Was looking into BeeksFX, but not really sure what to look for.
@vince.stans