Any updates on this issue? It's affecting us on our VPS as well. cTrader keeps “losing touch” with running bot instances as described in this thread. We discovered this two weeks ago when we were wondering why our bots weren't taking trades they were supposed to. They just “stopped” logging anything, but cTrader still showed them as running.
It's frustrating that now there's at least 2 users reporting this issue, and there still doesn't seem to be any movement on it even though I:
sent them emails (Screen captures above in this thread where they acknowledge receipt of the emails) in August on what the issue is and how to reproduce
provided them the exact source code I was using
provided them full access to my VPS with the bots running where the issue outlined in the emails happens all the time
provided them a YouTube video link demonstrating the issue and how I reproduce it
People would probablyt be more inclined to help you if you used the “insert code block” option and pasted in nicely formatted code instead of what you have.
And try to get somewhere close to how they are implemented in ThinkMarkets ThinkTrader as no other platform comes close to the exception way they've implemented their alerts.
They're all cloud-based, and can be set for any indicator and any option (price cross, indicator cross, indicator levels, etc).
I use ThinkTrader solely for this purpose because they're so excellently done, and being cloud based with push notifications (so they work on desktop, mobile, web, etc) it doesn't matter how we're logged into the app - we get notified:
You need to post this in the Suggestions forum. This is technical support, and Spotware doesn't come here to see what users are requesting for new features.
I hope you're not expecting a response and just posting a general statement because you've posted no screen shots, haven't mentioned the time it happened, or anything else.
I did not write that this does not happen, I wrote that we are not able to reproduce the "unexpectedly terminated" message on our machines on your VPS either. If we cannot reproduce it, then we cannot easily spot the problem. Also we cannot spend unlimited hours waiting for one user's problem to happen again. If you are able to isolate exact steps that will allow us to consistently reproduce this behavior, we are happy to have another look. Else it is a low priority issue and we will fix it if we stumble on it in another occasion.
Best regards,
Panagiotis
I explained how to do it in the video that apparently nobody from Spotware is willing to watch from start to finish.
I also sent them this email, dated August 20th, that I was acknowledged because they responded to it:
Proof of the acknowledgment of having received the email. THe “unexpectedly terminated” doesn't always happen, but what DOES always happen is the bots will “lose” their connection to cTrader. I've left the windows open in the VPS showing this. AUDCAD pair. cTrader says the bot is still running, but it's obviously not doing anything because it's no longer logging anything in the “OnTick” event. This is easily reproducible in the steps I've outlined in the above email screen capture. It happened for your team as well – just look at the logs from when they started the bots. They should see several bots are still running, but cTrader “lose” them because they are no longer responding/logging.
I did not write that this does not happen, I wrote that we are not able to reproduce the "unexpectedly terminated" message on our machines on your VPS either. If we cannot reproduce it, then we cannot easily spot the problem. Also we cannot spend unlimited hours waiting for one user's problem to happen again. If you are able to isolate exact steps that will allow us to consistently reproduce this behavior, we are happy to have another look. Else it is a low priority issue and we will fix it if we stumble on it in another occasion.
Best regards,
Panagiotis
I explained how to do it in the video that apparently nobody from Spotware is willing to watch from start to finish.
I also sent them this email, dated August 20th, that I was acknowledged because they responded to it:
Just wanting to confirm you've received the messages I've sent? If not, I think Spotware's email system is blocking them for some reason because all my initial messages got through to the Community team - obviously since they asked for the VPS' details to check out the issue.
Thank you
Hi firemyst,
Messages received, the team will check later this week or early next week. Thanks for your patience!
Best regards,
Panagiotis
Any updates? HAve they been able to see what's going on?
Hi firemyst,
Unfortunately our engineers were not able to reproduce the "unexpectedly terminated" on your VPS either. So at the moment there isn't much we can do.
Best regards,
Panagiotis
This is from the VPS as it is right now. I've left these windows open.
I can't make it any more obvious what the problem is.
Just wanting to confirm you've received the messages I've sent? If not, I think Spotware's email system is blocking them for some reason because all my initial messages got through to the Community team - obviously since they asked for the VPS' details to check out the issue.
Thank you
Hi firemyst,
Messages received, the team will check later this week or early next week. Thanks for your patience!
Best regards,
Panagiotis
Any updates? HAve they been able to see what's going on?
Hi firemyst,
Unfortunately our engineers were not able to reproduce the "unexpectedly terminated" on your VPS either. So at the moment there isn't much we can do.
Best regards,
Panagiotis
IT WAS RIGHT THERE. ON the screen in the open session as I left it. If they watched the video, they would have seen processes were still indicated as “running” but WERE NOT logging anything on every tick. Eg, they stopped, or “got lost”, or something, but were no longer responding.
Using the exact same source code I emailed them at the Community@Spotware account. I had it open. All they had to do was look and see.
Nobody actually watched the video did they? I see the youtube count didn't go up.
Just wanting to confirm you've received the messages I've sent? If not, I think Spotware's email system is blocking them for some reason because all my initial messages got through to the Community team - obviously since they asked for the VPS' details to check out the issue.
Thank you
Hi firemyst,
Messages received, the team will check later this week or early next week. Thanks for your patience!
Best regards,
Panagiotis
Any updates? HAve they been able to see what's going on?
If you wrote your own bot, then you do it in your code by modifying the position and reducing the volume of your position when your criteria are met.
Sorry for being unprecise, but I meant manual backtesting without a bot or even indicators. Just looking at the chart and using a little bit of intuition.
I am using hedging for some time now and you can get out of bad trades by partly closing positions quite well. But I can not do that in replay mode or I did not find the option to do this.
Just double click on your order in the order window and the modify order window comes up.
Reduce the volume of your position and click to update your order.
Telegram is not the place to report your issues. Your emails were not received. Your video has been forwarded to the product team for further investigation.
Best regards,
Panagiotis
@PanagiotisCharalampous:
Here's another report of your team not receiving emails people are sending to the “community” email address.
I think this should warrant some kind of investigation on Spotware's side to see why as there's now at least 2 users who had sent emails through, but Spotware didn't receive them.
To refresh, here's the thread on an issue I reported where after sending the initial issue to the Community addresses, they didn't receive any further emails from me once I tried sending through my VPS information:
firemyst
27 Sep 2024, 01:41
RE: RE: When a bot was "unexpectedly terminated", cTrader shows the bot as still running
zossles said:
It's frustrating that now there's at least 2 users reporting this issue, and there still doesn't seem to be any movement on it even though I:
@firemyst