43 Algos Stopped – Due to an Error!
- This topic has 19 replies, 6 voices, and was last updated 2 weeks ago by
.
-
When I hover over yellow icon in Order List, the reason for ‘Too many Retries’ is ‘Position does not exist’. No I dont know how to sort it, please elaborate?
External Event … yes I’ve had that loads over the years … seems to go in phases, not for months then several times in a week or two.
1 user thanked author for this post.
When I hover over yellow icon in Order List, the reason for ‘Too many Retries’ is ‘Position does not exist’. No I dont know how to sort it, please elaborate?
External Event … yes I’ve had that loads over the years … seems to go in phases, not for months then several times in a week or two.
Both should coincide;
First PRT errors out somewhere for a reason unknown and withdraws the position without being able to communicate it to IG and next IG touches a price (Limit/Stop), wants to do something with the running position, but the position has gone. It is not said that PRT was the first in error.
The External Event is logically in order with the former just the same because “something unknown” read : something unexpected, caused the position to close and this error should be initiated by IG (why ? because the chance is 99% that IG causes this because of the numerous other situations where IG causes it).Example of the latter : minimum distance is 106 points (yes, even that many occurred two days ago during Putin/Trump talks). Thus, IG manipulates, no system can deal with it, and PRT throws the error but the error originates in IG (and most certainly not in “you” which would be the technical cause following the computer systems).
The “problem” with most – if not all in this thread, is that it is from Demo-Live – totally unreliable for real happenings as reality lacks. So please keep in mind, I always talk from Live-Live and therefore the reasoning could fit. Example again : I may wonder whether the minimum distance as a reason will ever occur from Demo-Live. I’m inclined to think Not.
Something else (or maybe not), the more of these “unknown errors” I see pass by (from you and others) the more I start to feel that IG is just downing systems for maintenance or whatever, which is just not in the workflow of PRT. IG just “do it”, unless you ever saw a maintenance information and that the platform is unavailable. I did not. But what we should know is that for IBKR this happens very frequently and that *is* communicated to us. And actually it is so that we can not even start the PRT platform during these periods of time (mostly on Saturdays for longer or shorter periods).
And more news : I don’t think that any of you know of the “backdoor manipulation” built into PRT to cover for IBKR anomalies. For example around 06:30 AMST each day when IBKR herself resets. Thus, PRT just stops monitoring at at time (from 06:26 to 06:35 or so) because IBKR is not there to respond and just like this example (last post from you) where the communication with IG fails, it failed each day with IBKR just the same. Until this backdoor solution was created – now it is fine. Btw, I am not talking from my neck because I caused a change like this in PRT-IB myself. There are quite some more, but most things still in there are virtually impossible to solve. Back to IG ? nobody is working on these things because the path from us users to IG just does not exist. Not for me via PRT support, and also not for you to IG support and then … nothing. So IG is a loose running train in this realm.I am afraid that we have to live with this or these situations as I don’t see ways to improve further; I tell it more often – I have given up to hunt it or post explicitly about it. It’s just there e-ve-ry-day. If anything, someone should sue IG for their manipulation with the entries (like see below) because those are the moments the most can be earned with autotrading – but those are also the moments that your systems won’t enter position (and are even kicked out).
The days that we thought that posting in here would be helpful because PRT would read it and thus would take action, are by now years behind us. Better accept it as it is and don’t be annoyed too much ?
1 user thanked author for this post.
I had the same thing this weekend again. All my algos stopped due an error, looks like there was some issue on PRTs side again. All of my positions were left open and unmanaged,
If anyone is interested: I will get re-imbursed by PRT for the algos that should have hit the stop loss. Thats good atleast, even though I wont get re-imbursed for the missed gain of the stopped algos.
Find exclusive trading pro-tools on 
