IB API "goodAfterTime" is not working?

trend2009 · Dec 5, 2019

I tried to send order with goodAfterTime="20191205 09:39:45". the order can not submitted. anyone successful using this field?

btw, I can successfully use goodTillDate.

nooby_mcnoob · Dec 5, 2019

trend2009 said:
I tried to send order with goodAfterTime="20191205 09:39:45". the order can not submitted. anyone successful using this field?

btw, I can successfully use goodTillDate.

You probably need a ISO-formatted date. Usually looks like YYYY-mm-ddTHH:MM:SSZ" for UTC

southall · Dec 5, 2019

I use "hour:min:sec timezone" on the same day

eg: "10:00:00 GMT" ,

i dont pass in a day if it is on the same day.

d08 · Dec 5, 2019

'20191205 22:14:00 EST' would be the correct format for today. TIF field must be DAY or GTC.

trend2009 · Dec 5, 2019

d08 said:
'20191205 22:14:00 EST' would be the correct format for today. TIF field must be DAY or GTC.

the tif field is "DAY". it did not work.

trend2009 · Dec 5, 2019

southall said:
I use "hour:min:sec timezone" on the same day

eg: "10:00:00 GMT" ,

i dont pass in a day if it is on the same day.

tried it, did not work either. the ib api was downloaded 10 years ago, do not know if it is too old.

trend2009 · Dec 5, 2019

nooby_mcnoob said:
You probably need a ISO-formatted date. Usually looks like YYYY-mm-ddTHH:MM:SSZ" for UTC

my format is correct.

d08 · Dec 5, 2019

trend2009 said:
tried it, did not work either. the ib api was downloaded 10 years ago, do not know if it is too old.

Why would you use something that old, why not just update? I can confirm the format I posted works. Maybe you're posting it too close to the trade time or too close to the close. I believe it's not allowed in the last minute before the close and there's probably other limitations as well.
Also, why not read the error messages that are returned?

nooby_mcnoob · Dec 5, 2019

d08 said:
Why would you use something that old, why not just update?

Obvious reason is: if it's working, don't change! But it's not working, so maybe change?

trend2009 · Dec 5, 2019

d08 said:
Why would you use something that old, why not just update? I can confirm the format I posted works. Maybe you're posting it too close to the trade time or too close to the close. I believe it's not allowed in the last minute before the close and there's probably other limitations as well.
Also, why not read the error messages that are returned?

I did not update api because the new api needs vc++ 12.0, which i am not familiar. I am still using vc++ 6.0. I think tws api version does not affect the execution because no matter what api version is used, IB only sees the text transmitted. the error message says "the correct format should be blah blah..." which I am already in correct format.