开云体育

Valid point. There are enough active traders here that anything widespread would probably get a mention. It could be something affecting only certain instruments. Hope it all goes back to normal for

HI Nick, I agree that not to much emphasis should be placed on paper trades. However, in all my experience over the years, IB paper has been a fairly accurate barometer of live trading. I'm only

Everyone has different experiences but I don't think you can make meaningful connections between fills on paper account and live. You just don't know what would have happened on live. If you are

And yes, the order is for 2300 shrs, but I should've received at least a partial fill. Am I in error?

Here's the jpg attachment of the 5 sec chart.

HI All, I experienced a no-fill (as of now) on the paper trading system today on a STPLMT bracket entry order: OSTK 2330 Shrs short TRIG: 48.22? LMT: 48.22 The trigger fired at about 9:40 AM and

The first step is to enable api logging and look to see when the order arrived at TWS. This will give clues as to whether the issue is in TWS or on the client side.

Waiting for the nextValidID callback before calling other API seems to have fixed the issue. Thanks for your help. ________________________________ Sent: Tuesday, March 22, 2022 8:17 PM To:

On live account, today, I experienced API order not showing up on TWS for quite some time, and by which time, the targeted price moved away. And similar order, entered through TWS interface executes

Hi Jürgen, Thanks for the reply! I'm running stand-alone older TWS version Build 981.3c, Jun 29, 2021.? Win7. Old dual-processor Lenovo E545, 12GB RAM, 256GB SSD. It's not a deal breaker since

That's about the time when our TWS restarts take place as well, Lou and we did not have an issue for a long time (maybe a couple years). Are you running "standalone/offline" versions of TWS or the

Hi Mark, Thanks for the input. Can't swear to it, but yeah, the "soft token" error might be it. I just rebooted the computer yesterday evening about six, so it shouldn't complain about the Sunday

I get a "soft token" error where it complains about expecting a different token every sunday. I assume this is when it expires the week long session token. Is that what you are seeing? Best

Hi All, I've been experiencing problems with the TWS auto-restart options, I'm getting some type of "token error" and have to completely shut down TWS and manually re-start it and manually log on.?

Short answer: no. Longer answer, you could run a flex query to get the P&L on the two legs and add them.? The call and the stock will have their own P&L, and aren't fundamentally linked from an

Crow, the issue with your code is not the .setConnectOptions("+PACEAPI") call. It is rather the location (timing) of the reqPosition() and reqMarketDataType() calls. You might want to reread the

I submit 50 every 1015ms.? A list of messages is managed by a thread that also maintains a list of timestamps for the last 50 submitted.? I haven't had a pacing problem in years.

The attached Java sample will connect to TWS, but then immediately disconnect (printing "Connection Closed") when I have m_client.setConnectOptions("+PACEAPI"); uncommented. After that, I can

I believe the OP is asking if the limit can avoided, not whether the error can be avoided. Pacing the requests does not avoid the limit but does avoid the error.

Let's say I hold a stock with a covered call. The stock rises over the strike of the call??and the option expires in the money => the stock is called away. Is there a way to get the pnl of this