- ago
2174: Warning: You submitted request with date-time attributes without explicit time zone. Please switch to use yyyymmdd-hh:mm:ss in UTC or use instrument time zone, like US/Eastern. Implied time zone functionality will be removed in the next API release

0
1,213
8 Replies

Reply

Bookmark

Sort
Cone8
 ( 6.30% )
- ago
#1
Do you happen to remember what request you were requesting?
0
- ago
#2
No
0
MIH8
- ago
#3
I believe I have seen this message before. If I remember correctly, it appeared in my data manager when I was doing updates. Maybe this helps to get further. I can only vaguely remember it, though, so that could be wrong.
0
- ago
#4
It happens when a trying to stream a chart with IB on it as the provider
0
- ago
#5
QUOTE:
It happens when a trying to stream a chart with IB on it as the provider

It would be pretty surprising to get such IB specific error using any other streaming provider 😂 Not much but at least that's a start.
0
- ago
#6
In response to @Cone's first post, I provided the EXACT time the event occurred
0
Cone8
 ( 6.30% )
- ago
#7
What symbol were you requesting and what time zone are you using for it in Markets & Symbols?
0
- ago
#8
I just saw this error today, I'm using TWS API directly from Python. To request historical data, you don't give IB a start and end time for the data, you specify only the end time and then (among other parameters) specify the size of each bar (1 minute bars, 15 minute bars, etc.) and how many bars to return.. If the end time is "right now" the date/time is left blank!

So if you are pulling up a chart that runs up to current day, you probably won't see this message (it'll leave the time blank); if you are doing anything that involves current stats, you won't see this message (either not using historical data at all, or pulling historical but recent data where the end time is blank.). Where you would see it is pulling up charts that are all-historical (end time on the chart is in the past), and in doing historical backtesting. I found having this request be in local timezone to be odd the say the least, I'm converting my code to use US/Eastern ASAP! Hope this helps!
-Henry
0

Reply

Bookmark

Sort