I have a theory …
If a System code takes > x nano or > x milliseonds to run, ProOrder Rejects the System with the Rejection Message as attached.
I confirm that my code includes DefParam PreLoad Bars = 10000 and Period of Indicators is <= 100.
I tried on both Demo and Live Accounts and several different Timeframes and Times of the Day … System Rejected every time!
Anybody else ever had the same / similar thoughts or experiences?
#LAURENT
Only post in the language of the forum that you are posting in. For example English only in the English speaking forums and French only in the French speaking forums.
Thank you 🙂
Hi GraHal,
No, that won’t cause this error (but various anomalies and only when the code takes longer to run than your bar length is (min. 1 sec)).
The problem you announced is general since at least Sunday night (after opening). I reported it yesterday morning and I suppose they are working on it, but I will ask in a minute.
The fun with this error is : keep on trying. Just re-hand the System to ProOrder until you drop dead. Yesterday it took me 90 minutes to “know” that they kept on running (experience : give it 10 minutes on a 1 minute bar) to be quite sure it won’t be rejected.
For me it happens in two IB accounts and two different Systems. IG I did not try.
Happy Starting !
;-(
Here’s my “rate” for one account (bottom part is now shown).
In the end I thus managed and all systems really traded.
I just told PRT that it happens for IG as well. And on Demo. I suppose PRT has “upgraded” their server software.
I just started 6 Systems with 2 different codes.
5 are the same code and are on 6, 10, 12, 20 mins and 1 Hour TF. The 6, 10, 12 and 20 mins TF versions have all been stopped (H1 TF not tried to run yet) at the first run of the code with the Rejection error I posted above.
Peter, please let us know when your sources say the problem has been fixed and I’ll restart them all again (for about the 6th time, so frustrating and demoralising!?).
The problem you announced is general since at least Sunday night (after opening).
I assume you have Systems Rejected (since Sun night open – for insufficient historical data) that have been running fine previously?
My Systems which have been Rejected (since Sun night open – for reason above) had not been run prior to Sunday night open.
I await your notification that all your Systems are running as normal before I investigate mine any further.
Mine are, as I type, still being Rejected for insufficient historical data!
I assume you have Systems Rejected (since Sun night open – for insufficient historical data) that have been running fine previously?
Correct.
I await your notification that all your Systems are running as normal before I investigate mine any further.
Hmm … But I can’t check that because they’re running now and I won’t stop them.
I should hear back from PRT as they know nobody (?) can start any Autotrading right now. If I don’t hear anything from them today, I will give a reminder again first thing tomorrow morning.
nobody (?) can start any Autotrading right now
I started a 5 sec TF System about 3 mins ago so it’s had over 30 executions of the code and it’s not been Rejected.
Still fine ?
In that case you see it can work, like with me. But by what coincidence ? beats me.
My Vector was also rejected several times today. But only that. Maybe complex calculations are sometimes a problem?
Peter, yes the 5 sec TF System continued running for a few hours, but I had to stop it as I needed the space for testing others (dang 25 System limit!).
Maybe complex calculations are sometimes a problem?
I think this is what is the problem with mine also!
Also there should be more specific Rejection error messages?
I think a few error messages cover too many problems and don’t help us at all. We look for what the error message says and this may not be the source of the Rejection at all, for example … not enough historical data!??
Historical data… was the error message for me too. But specifically with the Vector I need 15 candles…I definitely think they were there. 😉
Haha 6 min TF Strategy Rejected at 08:18 for insufficient historical data. Same strategy was Rejected loads of times yesterday for same reason.
Same Strategy, but with reduced complexity (I woke with good ideas!) has just ran at 08:24 and 08:30.
I have a theory …
If a System code takes > x nano or > x milliseonds to run, ProOrder Rejects the System with the Rejection Message as attached.
Conclusion, at this stage, is that my Theory is correct!
Yeah, that is why my systems with 4000+ lines of code also run.
Man, you need to try harder. 🙂
Anyway, of course there can be something ‘in it”.
I know that at the same time (say end of last week) they changed something with Memory for at least me. I asked whether this has been done for everybody, but no answer.
Try one which fails and make a Technical Report of that. Then tell me here whether that has been been done. Put the text @Johan in there.
What is the nature of the “complexity” you removed ?
