There was something. You know I'll need to check that. Quick search says Master API client ID - The API client with the specified client ID will receive all orders, even those placed by other API clients. This differs from the Client ID of “0” which will receive all orders sent from the TWS GUI. But I'll need to check it on real account.
@@MLAlgoTrader I learned that reqAllOpenOrders returns all open orders created by all client ids. However, only the client ID created the order can update cancel it.
Oh sorry you are completely right! I didn't see this comment. My new video shows I don't know what I am talking about. Apparently clientId=0 is needed to see the orders made by phone. ruclips.net/user/livetfBfWWRkLQw
Code: Code: github.com/adidror005/youtube-videos/blob/main/Never%20Let%20a%20winning%20trade%20turn%20into%20a%20loss!.ipynb
Pretty cool. I like the way the code is structured. I can see a lot of value in this pattern. Thanks!
Reminds me I need to upload to git now.
Is there any advantage when you choose clientId=0?
There was something. You know I'll need to check that. Quick search says Master API client ID - The API client with the specified client ID will receive all orders, even those placed by other API clients. This differs from the Client ID of “0” which will receive all orders sent from the TWS GUI.
But I'll need to check it on real account.
@@MLAlgoTrader I learned that reqAllOpenOrders returns all open orders created by all client ids. However, only the client ID created the order can update cancel it.
Oh sorry you are completely right! I didn't see this comment. My new video shows I don't know what I am talking about. Apparently clientId=0 is needed to see the orders made by phone. ruclips.net/user/livetfBfWWRkLQw