Trade not executed / Issues with historical data
If trades in OptionsApp are not executed as expected, or if you experience unusual delays or errors (e.g., "loop runs forever", "no matching strikes found", ...), this is often caused by an issue with historical market data in TWS.
This problem can occur when TWS gets into a corrupted state in the background, for example, if the connection to IB servers was temporarily interrupted. Even if no specific error message is displayed, this can significantly impair OptionsApp's data queries.
Typical causes for this condition are:
- Brief interruptions of your internet connection, which temporarily cause a loss of connection to IB data servers.
- Manually restoring a layout in TWS ("restore layout") while it's running.
- Your PC or laptop goes into standby mode or activates power-saving features. An active screensaver can also be problematic for TWS and its state.
- Simultaneous logins to the same IB account from another device, this automatically disconnects existing connections.
- Unstable WiFi connections or very weak internet signal, which can cause unnoticed disconnections.
Important: Once any of these factors occur, TWS often remains in a corrupted state regarding historical data, even if everything appears to be working fine. Historical data is then either not delivered at all or delivered incorrectly.
🔁 Our recommendation: In this case, completely close TWS (not via the internal "restart") and also close OptionsApp. Then restart both. Only this way will the state be completely reset and TWS will deliver the necessary historical data for OptionsApp again.
💡 Note: For maximum stability, we recommend running OptionsApp on a dedicated server. This avoids typical issues like standby, network interruptions, or user interference and ensures a clean connection to TWS around the clock.