Summary
After upgrading to the current version of ibflex, which uses the IBKR Flex Web Service v=3 endpoint, I noticed that one of my existing predefined Flex queries started returning only the last business day. Previously, the same predefined query returned my expected time scope, which was 365 days.
Workaround
Create a new Flex query in IBKR Client Portal with the desired report period, then use the new Query ID / Reference Code with ibflex.
In my case, recreating the query restored the expected 365-day report period.
Notes
This is no an ibflex bug. It may be related to how IBKR handles existing predefined v=2 Flex queries when using the new Flex Web Service v=3.
The Flex Web Service API request itself appears to expose only parameters such as token, query ID, and version. I did not find a way to pass the report period directly through ibflex or the Flex Web Service request.
Summary
After upgrading to the current version of
ibflex, which uses the IBKR Flex Web Servicev=3endpoint, I noticed that one of my existing predefined Flex queries started returning only the last business day. Previously, the same predefined query returned my expected time scope, which was 365 days.Workaround
Create a new Flex query in IBKR Client Portal with the desired report period, then use the new Query ID / Reference Code with
ibflex.In my case, recreating the query restored the expected 365-day report period.
Notes
This is no an
ibflexbug. It may be related to how IBKR handles existing predefinedv=2Flex queries when using the new Flex Web Servicev=3.The Flex Web Service API request itself appears to expose only parameters such as token, query ID, and version. I did not find a way to pass the report period directly through
ibflexor the Flex Web Service request.