Troubleshooting

11 articles

Connection Problems OptionsApp to TWS

1. Checking TWS Settings and Live Data If you're experiencing connection issues between OptionsApp and Trader Workstation, please check the following points: 1. Make sure the API settings are configured correctly (correct port, Read-Only API disabled, ...). Feel free to

Error Message "Market Unknown"

In your OptionsApp Dashboard, you'll find the market status display in the top right next to the trading day selection. Normally, the current market status for your selected Underlying (e.g., SPX or SPY) should be displayed there. However, if Market: Unknown is shown, this means the following

Request IB Server Change (zdc1.ibllc.com)

Issues with non-European server connections It has been found that many problems occur with accounts connected to a non-European IB server (e.g. ndc1.ibllc.com). Connecting to the European server zdc1.ibllc.com (Zurich) often provides significantly more stable

My trade is not appearing in the Dashboard

In OptionsApp, planned trades are only displayed in the Dashboard under certain conditions. This display is dynamic and depends on whether the trades can actually be executed. The following are the most common reasons why a trade may not appear in the Dashboard

Issues with automatic restarts or OptionsApp freezing on Windows servers

1. Overview and Typical Symptoms In some cases, OptionsApp may appear to shut down on a Windows Server on its own, freeze, or restart multiple times per day. This behavior occurs particularly during continuous operation (e.g., on Strato servers or other Windows

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 running forever", "no matching strikes found", ...), this is often due to an issue with the historical market data in TWS. This problem can occur when

Trades are not being executed (Trade could not be submitted)

1. Status Display in Dashboard: "Strikes" Column In the OptionsApp Dashboard, the "Strikes" column provides a quick overview of your trades' status. It not only shows the Strike(s) of an active trade, but also explains why a trade wasn't executed. 2. Meaning

Troubleshooting Checklist for Problems

This checklist guides you step by step through the most common causes when OptionsApp isn't working as expected. In practice, issues can usually be categorized into one of two types below. Overview of checklists CASE 1: Problems with the connection between TWS and Op

TWS is frozen ("No response") or heavily overloaded

Some users report that Trader Workstation (TWS) becomes heavily overloaded, completely freezes, or experiences synchronization issues when used with OptionsApp. This manifests itself, for example, through persistently high CPU usage, increasing memory consumption, or the message "No response"

Overlapping Trades in OptionsApp: The Difference Between Gross and Net Positions

1. Overview If multiple trades in OptionsApp involve the same options contract (Leg), position overlaps can occur. This happens, for example, when a later opened trade uses a Strike that is already contained in another trade, such as a Long in a

Unmanaged Trades - Manually Managed Positions

1. What does "UNMANAGED" mean? A trade is treated as "UNMANAGED" when OptionsApp cannot clearly match its own saved trade state with the actual position in your TWS account. Possible causes include, for example: Important: Marking a trade as UNMANAGED does not change