To me it seems that you don’t know how to look up the real cause ? Exceeds-the-cumber-of-retries is no error and mentioning it is hardly useful this way.

Thus, retries of WHAT ?
Example below.
🙂

image_2023-03-27_105838018.png

Thanks for trying to help Peter.

Out of 13 Systems that I started about 2 hours ago, 7 have since opened trades so it is not as if there is anything intrinsically wrong with the code (thus resulting in Rejections).

My 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!

GraHal wrote:

Others 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.

GraHal wrote:

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).

GraHal wrote:

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).

image_2023-03-27_155121081.png image_2023-03-27_160502897.png image_2023-03-27_160805381.png

I 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! 🙂

ONCE A2 = 11.0
ONCE B2 = 21.0
IF NOT OnMarket AND Hour > A2 and Hour < B2 THEN
BUY 1 CONTRACTS AT MARKET
ENDIF

I will investigate further and ask for help accordingly.

Re above, I had a Sell and a SellShort with the same conditions, this may have confused PRT.

Anyway as a result I’ve killed off the System referred to above and improved the strategy overall.