Don't use version 10.30 (even if it's the current stable version). This issue is fixed in versions 10.31 and newer. It didn't exist with versions 10.29 and older.
The problem started with TWS version 10.30 and since stable version rolled from 10.19 to 10.30 a few days ago, you have started experiencing the problem just now.
This is why one should always prefer the offline versions of TWS that do not automatically update (even while using the stable version).
Here's a list of my findings.
I have experienced this issue myself with API clients that use older versions of the API.
The problem triggers in the orderStatus callback. In the newest APIs, the orderStatus callback sends Decimal fields (instead of Integer) for filled and remaining quantities (openOrder does too but in the Order object).
Months ago, I have contacted IB to ask if a TWS API setting could be introduced to maintain compatibility with older API clients but my request was denied due to lack of demand.
I decided to start upgrading my applications to use the newest API.
Later, I found that TWS version 10.31 and 10.32, for some unknown reason, do not trigger this error.
Stable version is currently 10.30 but it has this issue with older API clients, specifically, in the orderStatus callback.
I have also found that there is a thread in this group that mentioned this issue:
/g/twsapi/topic/107023187Hope this helps.
--
