Suspicious orders by IG
Forums › ProRealTime English forum › ProOrder support › Suspicious orders by IG
- This topic has 9 replies, 3 voices, and was last updated 1 year ago by Nicolas.
-
-
09/11/2023 at 12:50 PM #220725
Last night I was running the
- GBPJPY MINI 15M
code and it made a series of suspicious long orders DURING a gap. The losses were significant and didn’t match any backtest. Something is clearly rotten in how IG is handling preorder requests, and something needs to be done about it
09/11/2023 at 12:52 PM #220727FYI
Attached is a non-exhaustive list of the elements that can impact a live trading strategy and create differences with a demo account and/or backtests:- Spread
- Slippage
- Orders rejections due to one of the above reason, but also because of the allowed distance from current price to put pending orders (known as “minimal distance”)
- Different trading hours (ProOrder code launched in a different time zone / custom hours, by the user)
- Coding problem: division by zero error, null or negative periods for indicators, ..
- Lack of responsiveness of IG demo servers (if IG is the broker), although this has improved considerably since last year.
- Make backtests without tick-by-tick option
- “set stop trailing” instruction that give IG the total control of your stoploss, can be moved differently between accounts due to points above
- Limited risk accounts and their rules
- Guaranteed stoploss rules and fees
- Starting a strategy at a different time (1 hour or even 1 minute later): depending on the code of the strategy, the results of some calculations could be different.
- Margin required on the trading account (no demo or backtest tests are made on this subject)
- Overnight and overweekend fees
- Automatic adjustement of stop orders checked or not when launching the ProOrder
- Minimal distance used in backtests for pending orders, not the same as in real trading, due to broker requirement
- Different contract size between backtests and live
Because backtests are only tested on history *with no connection to live market* , you may encounter differences with real live trading environment subject to spread enlargement, slippage, etc. If your stop hasn’t move, there must be information of an error into your orders rejected list you can consult with CTRL+O.In any case, first step is to compare the backtest orders with the real orders, and why they triggered not at the same time/differently.09/11/2023 at 1:27 PM #220731Hi nightjimbob,
Sorry for your unexpected losses.
I would stipulate a situation like this : The best day for ProRealTime (not) – all fails
Even more so, because PRT refused to tell the reason (which I more than explicitly asked and I am usually told everything – not so this time).09/11/2023 at 1:46 PM #220735You will know better than I whether this tells something or not :
Your 15 minute TF chart/system, starts to go off of the 15 minute boundaries where you see the mouse arrow. For example, of your exits are Pending Stop orders, then this can be fine and the few on the 15 minute boundary are a coincidence (you trade at the wrong side of the price, “wrong” between quotes). But might you say that you are only executing Market orders (for the Exits, if I look correctly), then the issue is the same as 3 weeks ago.
09/11/2023 at 1:52 PM #220737That is very distressing to hear. It is hard enough to make it in trading without your broker and tech provider loading the dice against you
09/11/2023 at 1:56 PM #220739Yes. But as long as we remain to have the idea that no broker or anyone is doing these things on purpose, we should be fine between our ears. Now it only needs to be prevented a next time.
What about those 15 minute boundaries and market orders, please ?
(per my previous post)09/11/2023 at 2:18 PM #220744People are losing thousands of euros a day because of this and it needs to be escalated urgently – unless Ig wants it to continue
09/11/2023 at 2:25 PM #220745Could you please post your code in order to understand what happened with the orders please? The gap happened before the first trade of your list, so I understand this:
series of suspicious long orders DURING a gap
Would need more investigation in your strategy, but it seems that you tried to open BUY limit orders at a price level above the current price, so they open directly and closed maybe with a stoploss or another condition based on your code.
You’ll get better explanation if code is posted, thank you.
09/11/2023 at 2:40 PM #220749The code is here: https://www.prorealcode.com/topic/free-profitable-strategys/
it is impossible to recreate the error with backtesting
im not bitter about fair losses – but this is beyond the pale and needs to be exposed by the fx press if something untoward underway
09/11/2023 at 2:54 PM #220754So that’s related to the strategy attached.
It puts pending limit orders from startTime = 210000 to endTime = 231500
In backtests, if I push a bit the spread used (>= 6 pips) to consider spread enlargment on Sunday and slippage due to minimal distance, there are indeed multiple losses in a row (see attached).
Sorry if I’m wrong, but IMO, I do not see any not expected behavior here 😐
-
AuthorPosts
Find exclusive trading pro-tools on