We still have to find out why the download has this issues in the newer versions.
My trading approach is based on Zorro 2.70 (64bit FXCM Plugin) and the failing lockback issue is still blocking me.

We have now tried to reproduce your observations and downloaded many MB in 32 and 64 bit mode from FXCM, but did not see any gaps or other problems. The FXCM server was as reliable as usual.

Maybe an unreliable Internet connection caused the problem. Or the FXCM server had an issue last week which was now solved.

Please get the latest release candidate 3.01.1 from the download page and run the following script in both modes:

function main()
{
Verbose = 15;
set(LOGFILE);
NumYears = 10;
assetHistory("GER30",1+OVERRIDE);
}

Then please send us the log and diag.txt.

I will do the test, but my Zorro S subscription was ending with 2.70. My setup (framework of many .cpp 64bit files + Python Gui) is running with Zorro-S functionalities. I had my errors in the beginning via trading (missing historical data during the LookBack), but then I recognised the gaps during the loading (Download script) of historical data.

Therefore, I have to test with the Zorro Free account, but I will do. I will use your script.

Martin

I have done several checks now. It seems, I had two issues at the same time.

1. Download gaps. I tested your files (3.01 for 32 bit) and (2.70 for 64 bit). I found no gaps and the diagnosis files were ok. I assume really server issues at FXCM these days?
2. Despite the fact that I had now updated .t6 files, I had still errors during the trade mode (64bit). Training and Backtesting worked fine. The history files are stored on Google Drive G:/ folder. And this was working without issues since years .
Now, I hardcoded the history folder in my script (History = "G:\\Meine Ablage\\11.2_Trading_Monitoring\\4_All\\History";) and now it works without issues.

My ZorroFix.ini has this entry: HistoryFolder = "G:\Meine Ablage\11.2_Trading_Monitoring\4_All\History"

Maybe it is an issue with Google Drive, but it works now. We can close this issue at the moment. If I see some further findings, I will report it here. Thank you for your support, you are doing a great job!