开云体育

Dear community, i have been working with the tws api client (c++) for more than two weeks now. Even after carefully studying the code provided by Interactive Brokers i couldn't manage to find a

well not 100% sure exactly why buti shut off the other instance of the same ticket symbol and just have one going. I watched the price move to the price level while order was cancelled and it was in

Thank you once again ! <TwsApiOnGroupsIo@...> wrote:

Ah I see, nice thanks

Glad you were able to fix your issue locally. When I referred to TWS logs, I was thinking about the encrypted logs you can access via the Help -> Troubleshooting -> Diagnostics -> TWSLogs menu. These

I can imagine there are more connectivity solutions once you generate "Sterling Trade Tech" levels of order volume. But it could be as simple as the FIX API the Trading API Solutions page (

tracking oder status... so i have orders open: the status: OrderStatus. Id: 7691 , Status: PreSubmitted , Filled: 0.0 , Remaining: 1.0 , LastFillPrice: 0.0 OrderStatus. Id: 7693 , Status: PreSubmitted

I have the following code which pulls out prices for multiple stocks in parallel from a REST api. not from IB. Then it places my orders in ib. results = asyncio.run(get_data(new_portfolio.keys())) app

is it possible to create a link that open specify symbol in TWS ?

For Interactive Brokers, placing stock buy orders using Java I need to have Trader Workstation running. I believe there is a web based IB Gateway API I could use, but it still all runs locally. So

can someone give and example code to use also ScannerSubscription and reqHistoricalData and reqMktData

I can try to help you

Buddy, Gordon and Jurgen - thanks. My thinking around holding the threads hostage was that 2 seconds 'should' be enough time to see an order canceled which it certainly is. However my specific case

I just uninstalled, deleted the entire JTS folder, reinstalled, and now everything works as expected. I probably had an unintentional setting checked somewhere, sorry for taken your time with this and

Hello, Thank you Jurgen for taking your time to test this. To answer your questions: * yes is a paper trading account linked to a real brokerage account where I have NASDAQ subscription. * account

Gordon and Jürgen are completely right, trying to use ```sleep``` to manage concurrency and synchronization will not go far. The correct(tm) approach needs to accept that **there is no shared memory

I am sure the delays you are experiencing are real, but I have the feeling that it is not just 'the paper account" that is at fault here. There must be some account attribute or setting that triggers

Honestly I would love to have no issues here, but in my opinion there is clearly a bug somewhere. 50 shares is a small amount for TSLA in my opinion. From logs I can see that the request is

Hear! Hear! Gordon is right on and the only pointer I can add is the TWS API Guide chapter Considerations for Automated Systems - Order Placement Considerations (

Main reason ordercall back making if full cancel confirmed.... this strategy time based thus I'd miss x trades which wouldn't work here. <bannerman1985@...> wrote: