Odd Historical Download bug - clears following day

[zstheorist]

If you Download historical Last minute data and don't end no Friday (since there is no trading on Saturday) it clears the next days data and leaves it with 1 minute of data.
E.g. If you Download July 3-6, 2022, July 7 will only have 1 bar of data - even if it was full before, but if you Download July 3-8, 2022 the week will fill in.
I am doing this with NT 8.0.27.1 (though bug was in at least versions since June as well I've realized) and IB data.

[zstheorist]

Addendum: The bug does not seem to roll to the next month, so if I load 7/28-7/31/22 it does not clear data in 8/1/22. Perhaps this is a database bug and not a download bug?

[NinjaTrader_ChristopherJ]

Hello zstheorist,

Thank you for posting.

Can you attach a screenshot of what you are seeing?

• To send a screenshot with Windows 10 or newer I would recommend using the Windows Snipping Tool.
  • Click here for instructions
• Alternatively to capture a screenshot press Alt + PRINT SCREEN to take a screenshot of the selected window. Then go to Start--> Accessories--> Paint, and press CTRL + V to paste the image. Lastly, save it as a jpeg file and attach this to your reply.
  • Click here for detailed instruction

Thanks in advance.

[zstheorist]

OK, I messed up a data set to show this to you. Originally I had data for VX 01-23 loaded from 1/2 through 1/6/23. I told it to download data from 1/3-1/4. It erased the data in 1/5 leaving a single data point (not the 1380 that should be there). I think this bug exists because the last data point for 1/4 is midnight (i.e. 1/5 12 AM). This happens consistently.

[NinjaTrader_ChristopherJ]

So I may look into this further please go to Help->Email Support and be sure to include Attn: Chris Jameson in the Subject line, a link to this thread in the body and a check in the box for "Log and trace files".

[zstheorist]

It has been a month since you reproduced the bug on your end. Have you figured out how to fix it yet?

[NinjaTrader_ChristopherJ]

Hello zstheorist,

I apologize for the delay. Unfortunately, this is technically currently expected within NinjaTrader due to the data load rules used when requesting historical data with different end dates over the same period of time.

Let me know if I may be of further assistance.

[zstheorist]

So, in short, you don't have anyone on your team that understands how your database was programmed. I hope you can hire someone soon who knows what they are doing. My original messages point to the most likely classes of routines that are failing.
This is a significant bug in your core database software. Your should fix it.