OHLC prices of QM U5 and QM #F

[clearpicks]

of yesterday bar are not correct.

[JayF]

Corrections have been made to the incorrect data, and our engineers are looking into what has been causing this problem in the last few days.

[clearpicks]

The problem comes again.

Originally posted by JayF
Corrections have been made to the incorrect data, and our engineers are looking into what has been causing this problem in the last few days.

[JayF]

Fixed. Our engineers continue to investigate the ongoing issues with QM.

[clearpicks]

JayF, could you tell me how eSignal determines the open/high/low/close prices of QM? It seems the openning price of QM is always not correct in the evening. Current local time is 21:45pm EST. It seems it uses the openning price at 15:15pm EST as the openning price when the local time is between15:15pm and 23:59pm.

[JayF]

The official opening price for QM is the first trade starting at 15:15pm, Eastern.

There is a bug that will appear for any symbol that trades on the current calendar day, but is actually for the next trading day. Essentially, the daily bar's Open/Close(settle) for "yesterday" gets wiped out and replaced with the Open/Close(last) starting from 15:15. This stays this way until 03:00, Eastern (midnight, Pacific), which is when the servers establish the new day's bar. At that point, the historical OHLC is correct on the servers for both days, and if you were running a chart overnight a reset (Ctrl-OK) would be required to refresh the chart data from the server.

In essence, the servers aren't aware of the concept of "tomorrow".

With that all being said, QM has been having an ongoing probelm where the servers haven't been picking up the OHLC. Our QA teams are cleaning them up each day manually, and the feed engineers are investigating why this is happening.

This is complex, so please let me know if you need anything clarified.

[clearpicks]

Can somebody from eSignal be designated to fix the prices of QM manually ASAP everyday morning after 10:00am before the problem is finally solved? Thanks.

[JayF]

This should already be happening. I'm checking into what happened this morning, and we'll get yesterday's bar fixed as well.