Rejected – More than allowed Number of Retries!
- This topic has 8 replies, 4 voices, and was last updated 1 year ago by
.
-
Sorry to hear this GraHal. Nothing of the kind happened over here. Maybe it is DJI-specific ?
And at your time (09:30) nothing exciting seems to have happened ? At 09:45 Yes, so maybe if your TF is 15 minutes ??1 user thanked author for this post.
Hi @GraHal. If you hover your mouse over the “i” part you get this clueless message that something went wrong. But . . . if you click the “rejected” word, you will get the reason behind the rejection. Screen captures are from French version, guess you will understand the essential. Good luck.
PRT / IG should make the space between Orders wider (by a few more milliseconds)??
Hi GraHal – I think that your situation is technically a kind of “impossible” as something could not happen (get through) in the first place. In addition (or *because* ?) I think that in such a situation something really is amiss. Like for example, you eating your own orders, if you know what I mean. Thus, it is you who places one order, and it can also be you who places an other order at the exact same time. But because both is “you” something rejects that.
I recall a live (though manual) situation that I had to close a Long for a Short I had on the same instrument in another (sub-) account, and that it was impossible to go out of the Short for logical reasons (no bidders). I had to go out of the Long, so I was the bidder myself on the Short. OK, this is not the exact same situation, but these forces are at play and the broker (the software) knowns instantly that it can’t go right – not even after a full second of trying.
… And there are so many situations that an order may fail …I can’t emphasize enough : If 100 errors occur in Demo, maybe 1 at most will occur in Live. This is with the same Strategy/Code.
I see virtually no errors (abends) in Live. And as you know … see below 1st attachment. BUT : What I do explicitly sit down for is eliminating each and every kind of error (killing the System from the server). Example : let all run around closing and reopening of the Indexes (so-called futures) and a couple of times per week you are too close to the price for whatever etc. Halt your trading around those times (just empirically found) and the errors disappear (obviously) with it.
I am not 100% sure about this yet :
During those very hours, the spread can be excessive. It seems to be *that* what is killing, because you may attempt to exit (set a Stop) which is within the threshold of the spread of that moment. This then including the huge jump an instrument may make at reopening or in that very silent time anyway (say between 22:00 and 23:00 your time), also knowing that nothing happens for real (markets are closed), but IG continues. See the example below (just after the weekend, but the principle is the same), where the jump is so high that together with the highest spread this just can’t work out (I never did the math but with a jump of 45 points and 5 points of spread in addition, you just won’t be able to start the position and set a stop right after).
N.b.: The trades you see here are all exists, and Yes that was beneficial. So you can go Out but should avoid going In.PS: I know this is not your situation really and just trying to present ideas which may get rid of all the system kills. How to know that something in Demo does not occur in Live is a matter of trying it in Live. 😉
1 user thanked author for this post.
Find exclusive trading pro-tools on 
