So Yes, I think I understand what you’re after;
What happens during CPI etc. announcements, is that things become too wild for IG and they need to fall back to “manual mode”. I know, this is hard to believe, but it causes the various types of orders (you put in) not to be processed for a while. I once had an experience of that close to two minutes lasting and this was only a simple (fixed) SL order. For the picturing of this :
Envision that the price goes through the roof (while you are Short) and it goes right through the SL and one meter above (ok, my monitor of concern really is 1m50 in height). Then things start to settle down there lonly at the top and then finally some person (!) dialing the knobs, appoints your SL to that price, and out you are. Say that your SL was at 100 but it goes out at 1000.
Remedy as I was told : get yourself the guaranteed SL and thus pay extra for each trade where a SL occurs in the program code. Note : IMO for a scalper this is too expensive, but alas.
So far, (not) so good.
Because your stops / limits on both sides of the price will be skipped per the very same means, you can thus end up at the wrong side with the wrong pending order type and you must now surrender to that person behind the dials for the when he/she deals with you(r order). If, for example, your code virtually becomes active again (in reality it is the broker) with a pending stop above the price, you are out in one go. No touching of the price needed. Meanwhile your Limit order also is there somewhere, and that may trigger an Entry again. How ? well, if this only happens within that same one bar you went out; I think it will be so that the limit order only is killed when that bar finishes. But instead of that happening, the order is filled again. And you ? you won’t understand, already because all goes too fast to follow. Only when you video-record things, you can later see how things went (I have a couple of video’s of such situations).
The moral should be that nothing can help against this.
Theoretically you can try to make an up to 1 second TF system of it, but I found that this makes things even worse. Thus, mind you, in such a situation you can’t even put in orders (of whatever type) and the “pending” mechanism causes or implies that each 1 second a new order is handed to IG (this is the nature of the pending orders, controlled by your program). All these orders will be a kind of queued, which is in the end a technical story with a relation to PRT, because it is PRT which can’t deal with orders which require feedback from the broker, which feedback stays out (lasts too long). And now even your system is killed from the PRT server.
I hope this made sense and shed some light on the (im)possibilities.
.
