Check for competing IBKR trading sessions under the same username. A direct IBKR login in TradingView is different from a webhook sent to PickMyTrade. Changing the local TWS socket port does not resolve a broker-session conflict.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Step by step
- 1 Note whether the disconnect happens exactly when you sign in to the IBKR broker panel in TradingView.
- 2 List other trading apps using the same IBKR username, including mobile and Client Portal.
- 3 Choose the trading session you need to keep active. Avoid repeatedly signing in elsewhere with that username during the test.
- 4 For PickMyTrade automation, check the webhook and desktop connection path described in its setup guide. A direct broker-panel login is not the same step.
- 5 If concurrent trading sessions are needed, ask IBKR about an extra authorized username and its separate market-data access.
A practical example
Suppose TWS works until you log in to the IBKR broker panel in TradingView. That timing points toward a login clash. A webhook-only alert does not require that same broker-panel step. Write down which path you are using. For the desktop path, the chart sends an alert to PickMyTrade and the desktop app talks to TWS. Changing the TWS port cannot fix a server that ends one login when another starts.
Screen reference
Start in Mosaic with File → Global Configuration. Then choose the panel named in the steps.


Mistake to avoid
Common questions
Does changing 7497 fix this?
No, if the broker is ending a competing login session.
Will a second username share all paid data automatically?
Do not assume so. IBKR says live usernames have separate market-data subscriptions.