Exactly, that’s what I mean. And that’s total bullshit… pardon the expression.
Yes phoentzs, I got what you mean. It’s been happing for quite some time now. I don’t know how to solve it, I suggest to tell PRT (as I will do). I usually simply close the previous backtest panels and start it from scratch.
It may help to stress that this is affecting many users. I already have a case open from a couple of weeks ago. It seems from your posts the issue goes back further than this but I guess the more they are aware that it is affecting lots of users the better …
My case is via IG Help and the reference is: 0013805.
I'll take care of it immediately and let you know. Thanks for your patience.
So, here are a few screenshots from me… One of my systems in M15 on the SP500.
In Figure 1 you can see the system in the backtest when it is started for the first time. The drawdown is incorrect and is a different value every time you restart it.
In Figure 2 you can see that there is no division into long and short trades.
Image 3 is the state when the report is updated. The overall drawdown is now correct, the division into long and short works… but… no individual division of the drawdown. It just shows me the total drawdown. That has nothing to do with the code either. It doesn’t matter what code you use. Ergo… the platform has a deep problem… with whatever. And it shouldn’t be like that. Especially not when it comes to money.
I confirm and reproduce the problem on the backtest reports (I haven’t seen the problem on the autotrading reports). The issue should be solved promptly.
Good news:
The issue should already have been resolved on the PRT SOFT & TRADING side.
The fix should be available on the IG DEMO & LIVE side early this week.
Thanks Nicolas, I’m on the IG side and I think a fix was rolled out this morning. I’ve tested it on a couple of different accounts and both seem to be OK now.
Ah …. spoke to soon! I am still getting instances of the long-short divided stats not calculating. It’s not consistent …. mostly all the stats generate correctly as they should do including the long-short divided stats , but a few times now the long-short divided stats have required a further manual click on the Detailed Report function to calculate. Screenshot below … same as the one phoentzs posted.
Is anyone else still getting this …. or any other errors?
I am still expriencing issues with the reports, as per my post above on 02/20/2024, I emailed IG chasing up to see if it is still live and they are still working on it. I got the reply pasted below. Before I reply with the URL for this discussion here, it woudl be really useful if anyone who has contributed and is still experiencing the same problem could add a quick update here too … the more info IG have on it the better.
Thanks for your email.
We currently don’t have any updates on the above, besides Pro Real Time saying a fix is in progress, we’ve followed up with Pro Real Time to see if we can get an ETA on this for you.
In your previous response, you’ve mentioned a PRT forum, would you be able to provide us with the forum URL and we can also pass that to Pro Real Time.
We look forward to your response.
The long-short divided stats are not calculating and never work unless I close the Detailed Report and then re-open and then hey presto the long-short divided stats show / can be seen.
We are all getting repetitive strain injury with all the additional clicking!
As long-short divided stats works after a close and re-open of the Detailed Report then surely it shouldn’t take long to fix?
The above same Issue has been going on for many months now and in the meantime is driving us all Batty! 😉
Thanks Grahal, I get exactly the same, and also the certain fields on the dashboard not filling … most often Max runup/drawdown and Risk Reward. Fix is the same, to click and regenerate the report. When Nicolas said they were rolling out a fix, it did improve things, the data is not always missing, but it hasn’t fixed it completely.
@Nicolas
Is there anything new here now? How do you deal with these mistakes?
Impossible for us to reproduce, I confirm that the fix has been deployed for a long time at IG v12… Please send us a new console via the platform's Help interface and add the link to the forum topic.
