Again 6 (!) strategies stopped!
Forums › ProRealTime English forum › ProRealTime platform support › Again 6 (!) strategies stopped!
- This topic has 86 replies, 7 voices, and was last updated 1 year ago by PeterSt.
-
-
03/27/2023 at 9:58 AM #21217603/27/2023 at 10:27 AM #212179
‘exceeds the number of retries’ is in intalics etc as it is a ‘paraphrase’ of the full Rejection message which is 45 words. I have been using ‘exceeds the number of retries’ all through this Topic.
If I go into the Order List and click on the yellow triangle for Systems Rejected for ‘exceeds the number of retries’ … it says – Quote Verbatim – Order Request failed. Please try again later. You any the wiser now?? 😉
Attached is the full 45 word Rejection message.
03/27/2023 at 11:00 AM #21218303/27/2023 at 12:53 PM #212185You any the wiser now?? 😉
Of course I am / we are. This already starts with me never having heard of *that* one and it proceeds with me by now having showed 20 or so different reasons of failure (on the very same “exceeds number of retries” – whether Number or Cumber -haha) and so …
So what could be the matter with *your* specific strange reason. Are you now telling that you never ever had a different reason than the one you you just showed ? … this is hard to believe …
It would be true that you never showed one (as if you refuse to to so).If you really have no other reasons to be found (ever) then we could try to blame your direct IG subscription, while I have a PRT-sponsored one.
?
03/27/2023 at 1:32 PM #212189My main reason for Rejection is / has always been ‘exceeds the number of retries’ .
My next reason for Rejection – but far fewer in number – is ‘broker can’t determine status of last order’.
We have had a big discussion somewhere re ‘exceeds the number of retries’ and you came up with some likely reasons for Rejection.
I am accepting ‘exceeds the number of retries’ as the ‘status quo’ on Demo Accounts, would love it not to occur of course!
03/27/2023 at 1:35 PM #212190your direct IG subscription, while I have a PRT-sponsored one.
Yes it may be that IG Demo Servers cannot cope with loads of Orders coincidentally and so Rejections occur.
Others on here have had ‘exceeds the number of retries’ so it’s not just me.
03/27/2023 at 3:04 PM #212219Others on here have had ‘exceeds the number of retries’ so it’s not just me.
Oh boy. I *also* have that !!
But there is always a reason behind it (20+ various). And you now showed ONE reason and tell me that it is always that reason. I don’t believe that, hence :we must be talking passed each other somehow.
Note please : I have always showed those 20+ whatever reasons not only including that reason of the time, but also with the full row of rejections. Each one (each yellow triangle) is one rejection. 10 in a row and – boom.
See screenshot in previous email.My main reason for Rejection is / has always been ‘exceeds the number of retries’ .
One more time : that is no reason as such. The reason is mentioned behind the yellow triangle. That 10 attempts were made to overcome the issue is something else and hardly of importance. But, it tells something about the cause;
If my order is rejected (and the system is killed) because of 10 attempts to wait for the distance of whatever being to close to the price, then something hopes that the distance is made larger, which … after 10 attempts in say 10 seconds, still did not happen. PRT (not IG) is not allowing to wait for this forever, and thus Boom you are out (done so by PRT – not IG).broker can’t determine status of last order’.
That is an entirely different kind of message BECAUSE no re-attempt will be done. Think about this – it is logic. Something is really in error now. This is 100% PRT error because while the broker is slow in responding, PRT can not deal with this slowness. If I (as a human) can’t determine the status of my (order) I run away screaming because I won’t be able to know what to do. Is the order still there ? is it filled ? was it killed ? etc. This does not require re-attempting. Something is wrong, period; no need to wait for a solution.
Would we pay attention, then we can learn from these “situations”. Example : Last Friday I had two of these very errors at the exact same time in two accounts on PRT-IB. So something goes wrong in the communication between PRT and the broker (reason : broker is slow in responding) and PRT announces the dreaded “don’t know last status” and kills your system. Yes, PRT-IB sucks too (almost even more so because it is about the only error on IB and I can’t do a thing about it apart from sending in 200 tickets about this – which I already told about and which I really did prior to AutoTrading with even 100x more emphasis on it now AutoTrading is in order with each few days this problem.More nice (not !!!) on this very error : this already happens when PRT-IB resets at 06:00 – 06:30 my time each morning because IB resets at that moment. If I then coincidentally have a Stop Order (for Take Profit) it’s BOOM again. So my code hence PRT sends in that Stop Order but IB is not there to respond (reset takes 30 secs or so). And you know what ? it was very hard to let this happen with manual trading because when IB resets, ProOrder is taken out of functioning on my screen. Thus, I can not *place* an order (all order labels will disappear from the charts and all order-place buttons the same). But now AutoTrading … you know, that beast which runs on a server somewhere and where my code tells at 06:13:13 to place a Stop Order.
See 2nd attachment for such a “morning failure”. The Order itself ended nicely, but the Stop order was still there – also not good at all.It is not good that PRT sucks on this aspect, but it is killing that nobody is doing a thing about this FOR YEARS (which is now 6 years in my case).
1 user thanked author for this post.
03/27/2023 at 3:24 PM #212224that is no reason as such
Okay I will check behind the yellow triangle each time from now on.
I will check 6 different Systems (re Rejections since Friday) behind the yellow triangle later today and report back, Can’t do now as Grandkids be here in 5 mins from school!!
1 user thanked author for this post.
03/27/2023 at 5:58 PM #212249I checked 10 different Systems and -behind the yellow triangle – it says in each and every case … Order Request failed. Please try again later.
But I noted 1 System that’s been Rejected loads over many hours! Strange thing is all the Rejections are outside of Hours which are limited by the code! 🙂
12345ONCE A2 = 11.0ONCE B2 = 21.0IF NOT OnMarket AND Hour > A2 and Hour < B2 THENBUY 1 CONTRACTS AT MARKETENDIFI will investigate further and ask for help accordingly.
03/27/2023 at 6:27 PM #212252Rejections are outside of Hours which are limited by the code!
Above was misleading / a red herring!
It is the Sell / Exit that got Rejected and Hours aren’t limited for a Sell (can be anytime).
03/28/2023 at 9:06 AM #21227703/28/2023 at 10:21 AM #212299Re above, I had a Sell and a SellShort with the same conditions, this may have confused PRT.
Nah, that won’t confuse PRT. 🙂 Just the last command (from top to bottom) is the one which counts.
So far I never rain into things ProOrder can’t cope with and fails on. Yeah, having Long and Short Systems on one Instrument like discussed today in the other topic. But then things are being done which the broker can’t cope with and PRT can not communicate over.It is quite convenient to know more than one broker. The one (e.g. IG) shows that things are technically possible, while the other (IB) fails on it. PRT can thus do it (while knowing that PRT may need adaption to either).
Knowing what fails on Manual trading is also very convenient; this tells readily what AutoTrading would fail on just the same (n.b.: I don’t have Manual experience with IG).
1 user thanked author for this post.
-
AuthorPosts
Find exclusive trading pro-tools on