API Support Forum
OEC API > API Support > AvgPositionList Position.Date or .Long.Timestamp and .Short.Timestamp zero
Author Topic: AvgPositionList Position.Date or .Long.Timestamp and .Short.Timestamp zero
(1 messages, Page 1 of 1)
Moderators: VPfau
jlanawalt
Posts: 88
Joined: Feb 12, 2009


Posted: Sep 21, 2012 @ 02:50 PM             Msg. 1 of 1
We have a demo trading account who's options orders time stamps are getting set to 0.0. We seem to get a valid number when the order is accepted and goes to working, but when the average positions changes or the account balance changes and we iterate the AveragePositionsList, we are finding that the Position.Date has a value of 0.0. If the Position.Net.Volume is long, the Position.Long.Timestamp can be zero, and if it is short, the Position.Short.Timestamp can be zero.

If we check the list moments later, in response to a user action, then we get non-zero values for those options orders.

Why would the Date or Timestamp fields be zero sometimes? What does that indicate. Is there a message we are overlooking that says "we are done updating the position's list, the time stamps are good again, check now."

Thank you