I found a strange behaviour with the FXCM 64bit Plugin. When I start Zorro (2.70) for trading, I get an NaD message in the LookBack run.
This behaviour I recognize especially for daily bars. In my example with asset GER30, I have historical data in the history folder available until 2008.
With the 32bit plugin I have no issue.
With the 64bit plugin:


AL09-G1-R2-1440-V1 start
Login 0 FXCM.. at UTC 01-21 19:24.
Error 047: GER30 1899-12-30 2026-01-21: 0 bars, 0 skipped, 500 needed)
Read AL09-G1-R2-1440-V1.fac
Read AL09-G1-R2-1440-V1.par......

Trade: AL09-G1-R2-1440-V1 2026-01-21
Assets AssetsStandard.csv
Lookback 500 bars, (NaD)..(NaD).

Also for other assets I can repeat this behaviour. It seems that the plugin does not collect historical data from the history folder during the LookBack period?

PRELOAD Flag is set. When I remove the PRELOAD Flag, for the shorter time frames the Broker data are loaded, but for the longer I get this error. Strange?

Martin

NaD means Not a Date, maybe it's something with the start and end date? 1899 12 30 is also an invalid date.

Start Date is 2011 and End Date 2026. Some assets work in this strategy and some not. BarPeriod=1440.
I checked the history folder, but these assets (.t6 files) are working for 32bit Zorro. Therefore the .t6 files cannot be corrupt. It seems I have an issue witch the Zorro64 and the Plugin.
But generally the most strategies under Zorro64 and FXCM-64 Plugin running, thats what is so strange.
I checked also the manual regarding error 47 and the dependency to LookBack and insufficient historical data...

If it only happens with some scripts, but not with others: Do they have something in common? Maybe some setting or a broker command?

I checked again the historical data. I found errors at two assets (GER30 and GBP/USD). I have renamed the historical data files for this two assets and started the reloading with the Download script (M1)
I just recognised an issue with the reload at FXCM:
Load GER30 2026.. 13306 min
Load GER30 2025..
Warning: 035 GER30 5 days gap Tue 2025-12-23 298248 min
Load GER30 2023..302668 min
Load GER30 2022.. 304899 min
Load GER30 2021.. 304168 min
Load GER30 2020.. 254151 min (gap 56 days)
Load GER30 2019.. 288296 min
Load GER30 2018.. 210536 min
Load GER30 2017.. 210475 min
Load GER30 2016..140831 min (gap 126 days)
Load GER30 2015.. 48432 min (gap 280 days)
Load GER30 2014.. 11959 min (gap 338 days)
Load GER30 2013.. 43652 min (gap 281 days)
Load GER30 2012.. 205660 min
Load GER30 2011.. 209220 min
Load GER30 2010.. 54419 min (gap 265 days)






Why do we have these gaps? This might be the reason for the further errors?. The download is done with the 32bit Zorro.

Yes, the gaps are way too large and will cause errors. Check the files in your history. A gap can be caused by appending new data to a file that already has gaps. Make sure that you have really renamed or deleted all old GER30 files.

Thanks for the feedback.
I deleted completely the files and even used via the ZorroFix.ini a different history folder (empty one). I did it today again and got other gaps in other years.
There must be an issue at the FXCM Broker? I am running the historical data since years and this is the first time I had this issue.
I changed to Zorro 64 bit, but the download runs via 32bit, which I already said. It seems is nothing with the Plugin itself, maybe an API issue?

If the download with the gaps was 32 bit with the download script, the problems have likely the same reason and are not related to 64 bit. It looks like a random stalling of the server. We had so far never a problem with the FXCM history, on the contrary, it was a rather reliable source.

I've forwarded the problem to the plugin developer. If we cannot reproduce it here, we will send you a special diagnostics version of the plugin that logs details of the problem.