The same data: 60 min wrong , 3600 seconds good.

[xTrader1]

Beta 20 and 22 , MB Trading Forex data feed.

Suddenly, several hours ago, 60 minutes bars of several pairs got wrong and had a wild values like 100000 or -7800 . Restarting NT on the same data gave another wild values but at another time and not for the same pairs. 59 min bars were initially ok, but afterwards were disturbed either.

Upgrading from Beta 20 to Beta 22 did not help.

Definition of data series as 3600 seconds instead of 60 minutes helped and the bars are clean.

It seems something got wrong with 1 minute data computation.
I'm in doubt whether the bug is reproducible, as every time a wrong bar appeared at another time and had another wild value.

I had a similar problem with Renko bars in earlier betas and the corrected bug was 0 volume bars not filtered out.

A question: Is it possible to cause NT to recompute minute values ? (of course except of exporting a data to history text files and reimporting).

[NinjaTrader_JoshP]

xTrader1,

NinjaTrader does not "compute" minute bars. They are provided by the data provider and NT just stores exactly what the data provider offers. What you can try is remove the old data from the Historical Data Manager and trying to download a new set. If that does not suffice then you will need to use the Edit tab and edit the bad entries directly.

[xTrader1]

xTrader1,

If that does not suffice then you will need to use the Edit tab and edit the bad entries directly.

But there are no bad entries !!! THAT'S A PROBLEM.

[NinjaTrader_JoshP]

Please export your data and take a screenshot of your chart and upload them here. Thank you.

[NinjaTrader_JoshP]

Also, in the next release there should be an overflow issue which could happen on high volume traded days that has been resolved. This fix may positively impact you here.

[xTrader1]

Also, in the next release there should be an overflow issue which could happen on high volume traded days that has been resolved. This fix may positively impact you here.

OK, may be that's an issue. Regarding "minute is not computed" - when importing history, we are asked "do you want to create a minute data" , so I thought it's the same with a real time data. For now I can live with a workaround, looking at 3600 second instead of 60 minutes bars, but a bug is hiding here.

Thank you.