Repeated “Forward Testing” Bug and Project Crash on EURJPY 2023 Backtest
Dear Forex Tester Support Team,
I am experiencing recurring issues while using Forex Tester during my backtesting sessions, specifically with the EURJPY 2023 project.
Recently, when running the backtest, the program became unresponsive at a specific point in time. After that, I have been unable to reopen the project — each attempt only displays a “Something went wrong” error message.
In addition, the “Forward Testing” bug continues to occur. The “Forward Testing” function frequently stops working, even though the project is not set to “Forward Only” mode. This issue has appeared repeatedly in the past and is happening again in this version.
Because of this recurring bug, the efficiency of my backtesting workflow has been severely reduced. I am unable to review historical records continuously within a single project, which disrupts my analysis and test progress.
I have already contacted support multiple times regarding this issue, but unfortunately, it still persists. Please advise on how to resolve this problem or provide an update on whether a fix is planned for an upcoming version. Could you please explain the cause of this recurring error (especially the “Forward Testing” malfunction) and let me know if there is a planned fix or available workaround?
Best regards,
Jason
- How does this impact your experience?
Comments4
Andriy Cherniyenko
Oct 16, 2025
Hello @User . Thank you for the bug report. I’ve sent the project link and described the issue to our developers, they’ve told me that this bug will be fixed in the next FTO release which will be implemented on 20th or 21st of October. The only workaround for now is to click “Rollback to previous save“ button and try to restore your project this way.
As for the inability to use “Forward Testing“ function (which was reported by you yesterday), the developers are still checking this problem.
I don’t think that the fix will be ready in the next FTO release, probably it will be done later (in 2-3 weeks after the release).
An Anonymous User
Oct 17, 2025
Hi, thank you for the update. I’ve tried using the “Rollback to previous save” button as suggested, but unfortunately it didn’t resolve the issue. I still can’t continuously review my historical records within a single project, which has significantly reduced my workflow efficiency.
An Anonymous User
Oct 24, 2025
Hi, just following up on the issue I reported earlier. You mentioned it would be fixed in the next FTO release around October 20–21, but I’m still seeing the same problem.
Could you please confirm if the fix was included in that release, or if it’s still pending? Also, the “Rollback to previous save” option doesn’t really work as a workaround in my case.
Thanks for your help!
Andriy Cherniyenko
Oct 24, 2025
Hello @User . Thank you for the update. I just spoke with our developers, and they said this fix didn't make it into the last release. It's been pushed to the next release, which is scheduled for release in a few weeks.