buddy

?

Sorry for the delay in replying. A minor matter of a respiratory infection that may or may not be COVID…

?

Yes, I know where your original instructions are, and I told you in my posts of 16 Sept 2022 that I confirmed the existence of the bug by doing the same thing in the VB sample program, rather than running your python script. I was asking again just in case you had updated anything.

?

The problem we’re facing here is that you don’t want to accept that I made a true discovery about the cause: you would much rather believe that, poor benighted Windows user that I am, I ‘messed something up’ by using a VB program rather than your script. Well, I didn’t mess up. Your comments at the time and since indicate that you never actually took the trouble to understand what I was doing, which was as ‘thoughtful and deliberate’ as it could be.

?

So your reaction maybe should have been ‘His workaround seems to work for him, why doesn’t it work for me?’ The next step would be to ask what’s different about what I was doing from what you were doing. And if you had understood anything about what I was doing you would have realised the big difference is that rather than running through a program or script, I was issuing API commands discretely. So necessarily there was a gap between the cancelMktData() call and the disconnect() call.

?

And as it turns out, that appears to be why my workaround doesn’t work for you, unless you introduce a delay between cancelMktData() call and disconnect(), as suggested by Ewald. With that correction, it seems to work fine (though you seem reluctant to admit it – so can you provide any examples of where it doesn’t help?). And in case you’re wondering, I installed Python to test both the original and the modified script.

?

You say:

?

Because of this, at the end of the day, I agree with Jurgen 100%:

?