Maybe IG have done a broker reset on UK Accounts only up to today?
Hope you get sorted soon.
I had loads of anomalies to sort out, e.g. loads were incorrectly showing + £65K ish or – £65K ish in the ProOrder non-running window … well weird!
Is there anything I can do myself? Can you create a second demo account on your own account? Is the problem with IG or with Prorealtime?
Pick your worst example and send in a Technical Report via the PRT Platform > Help > Help Center > I’m having a technical problem.
The Tech Report will go to IG, who if IG cant sort it then it will be forwarded to PRT.
Above will alert IG that you are still not fixed etc.
Looks like it’s still happening … 1 out of 20 running is showing stopping (had been running fine earlier today).
GraHal, how would that happen while at first it was fine, yesterday ? This would mean that the issue (title of this topic) changed from “System stopped due to an error” to “Systems won’t stop after they have been stopped/killed”. Am I right ?
Or didn’t you wear your glasses when you looked earlier and only thought all those pending stopping systems had been stopped now ?
😉
The problem appears on Monday with demo accounts of IG servers, due to an update these news issues arised. I will update asap about how and when it could be resolved for everyone..
only thought all those pending stopping systems had been stopped now ?
Yesterday, I painstakingly got 20 Systems running with none Stopping; then went and worked on my building project. When I came back 1 System was Stopping.
Pinhole glasses on before and after! 😉
You’ve got the wrong type !
Deffo still happening … 4 out of 20 are showing Stopping (was 1 out of 20 earlier today).
So this means that running systems get kicked out, still ?
(and then end in the status Stopping)
My situation is also unchanged. There has been no response to my ticket either.
Yes for me anyway!
I will call my contact tomorrow and will ask if they know anything about this in the first place. If Not, then no tickets come through to them anyway, although Nicolas should have this reported individually (if I understood correctly).
One important thing I have on my chest since I saw this happening for you :
The “Due to an error” is unique to me and the only other occasion that this happened was ~3 weeks ago when all LIVE orders went ballistic. This was then due to an upgrade on the server software, with no further explanation other than “we won’t tell” (a PRT response, not a PRT Support response). I took that highly, especially because I TOLD (yep) them to be honest. So they couldn’t.
Will let you know more tomorrow.
PS: Consider yourselves lucky that this wasn’t a Live situation, like ~3 weeks ago.
The “Due to an error” is unique to me
Maybe I should NOT have piggy-backed my comment on Stoppages this week onto this old Topic titled TS’s Stopped “Due to an error”?
I just looked back at Post No 1 and, yes Peter you are correct, when I started this Topic, Rejection message was “Due to an error” (I posted a screenshot).
This week’s Stoppages were due to an error somewhere, but most of my Rejection error message were ‘broker could not confirm status of last order’.
Problem occured to me again, I thought it was fixed. But same issue happend now. Even worse now as single algos have taken multiple positions..
