API Support Forum
OEC API > API Support > Issue pulling in most recent historical daily bar for Grains
Author Topic: Issue pulling in most recent historical daily bar for Grains
(11 messages, Page 1 of 1)
Moderators: VPfau
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 07, 2021 @ 01:50 PM             Msg. 1 of 11
Did something change with the way grains history is sent back?

We are having an issue where we are not getting the most recent historical daily bar for all grain contracts (plus soybeans/soymeal). All other contracts are pulling in the most recent daily bar fine, but it seems all grains are having issues.

We have had 3 reporters of this issue starting from the start of todays trading period (yesterday open).

Will you please look into this for me?

Thanks.
VPfau
Moderator
Posts: 134
Joined: Oct 26, 2011


Posted: Jul 08, 2021 @ 07:31 AM             Msg. 2 of 11
>Did something change with the way grains history is sent back?
No

Please contact our customer service and, if this is system issue, they will make a ticket for developers.
Thank you
Vitaliy Pfau
CMicciche902
Posts: 315
Joined:


Posted: Jul 08, 2021 @ 10:17 AM             Msg. 3 of 11
I'm not seeing a change in GAIN Trader Developer. Are you seeing the same issue in our latest COM samples? If not, what version are you using in your application?
Chris M
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 08, 2021 @ 01:38 PM             Msg. 4 of 11
I am seeing a historical bar come back, but it seems like there is something that is being sent back in a different order or something. I can't quite put my finger on it.

We have a data tab that we show all of the historical data and we have duplicate records for all grains, not for any other contracts.

We are only seeing the issue with daily historical requests, intraday seems to work correctly.

The GF COM sample code only seems to pull hourly historical data.

Both OEC Trader and Gain Trader are showing the daily bar correctly for grains.

I have tried the OEC API COM and the GF API COM and I am seeing the issue on both in our developer environment.

This seemed to happen over the holiday weekend, maybe there is something wrong there.
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 08, 2021 @ 02:13 PM             Msg. 5 of 11
It appears the grain contract start time is coming back incorrectly. The contract start time is coming back as 6 AM MST and close time of 12:20 PM MST when it should be a contract start time of 6 PM MST and close time of 12:20 PM MST.

Will you please double check this to see if my findings are correct?
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 08, 2021 @ 02:44 PM             Msg. 6 of 11
And now that I know what I'm looking for, the COM API sample shows ZCZ21 Start time: 6:00, stop time: 12:20 when it should be Start time:18:00, stop time: 12:20
CMicciche902
Posts: 315
Joined:


Posted: Jul 08, 2021 @ 04:23 PM             Msg. 7 of 11
Is this using the sample from https://bitbucket.org/GainFuturesDev/comapisamples/src?
Chris M
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 08, 2021 @ 04:49 PM             Msg. 8 of 11
Yes it is
SPikalov
Posts: 14
Joined:


Posted: Jul 13, 2021 @ 04:32 AM             Msg. 9 of 11
Hello.
The issue with the incorrect session time has already been fixed.
Please, download and install the latest version of GAIN GFAPI COM
x64: https://prod.gainfutures.com/WebAPI/api/Files/DownloadClientUpdateLast?brandId=0&clientTypeId=5005&branchId=2
x86: https://prod.gainfutures.com/WebAPI/api/Files/DownloadClientUpdateLast?brandId=0&clientTypeId=5003&branchId=2
And check again.

Thanks,
Sergey
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 13, 2021 @ 02:03 PM             Msg. 10 of 11
How did it just break COM OEC API if you have not been doing work on it lately? Further, then how are you not fixing the COM OEC API to fix the problem?

We haven't officially moved over to the GF API due to items that are needed in the COM GF API (such as prioritizing orders/positions coming back rather than a contract load that will cost clients time delay on order fills). We have been waiting on before moving to the COM GF API and this has broken our current clients in the COM OEC API?
RWare2020
Posts: 118
Joined: Feb 11, 2020


Posted: Jul 15, 2021 @ 12:15 PM             Msg. 11 of 11
The grain bar is coming in correctly now, but the open time is still incorrect.

I'm not sure how it got fixed, but thanks for taking care of that, we will keep our eyes open for the open time change.

Thanks.