I upgraded to v6.5.1000.5 yesterday. I am currently using the simulation account.
Daily, I have many open orders (perhaps 25-50). At the end of the day, I "Close" all orders. Last night I still had an open order, so when I Closed all orders, I also did "Flatten Everything", and still had to manually exit the final contract. This is all fine. (One note: my Closing of these orders was well after hours, into the evening. This is NOT my normal behavior. Perhaps this had something to do with what follows.)
This morning I found many orders re-generated and executed (perhaps 4, each of 3 legs). So I had trades execute upon NT launch, that had been cancelled last night.
In my Log I see 33-34 "Injected execution from log:Execution=..." lines. These are under the Category Order. They all began immediately after "Session Break" and before "Automated trading enabled". They took 4 seconds to do.
I appears that these could be the new orders that triggered at the opening. Could this be a bug in the latest version? Is there something more I should do to make certain that orders aren't lingering overnight, to fire off upon launching the next session of NT?
Brian1
Daily, I have many open orders (perhaps 25-50). At the end of the day, I "Close" all orders. Last night I still had an open order, so when I Closed all orders, I also did "Flatten Everything", and still had to manually exit the final contract. This is all fine. (One note: my Closing of these orders was well after hours, into the evening. This is NOT my normal behavior. Perhaps this had something to do with what follows.)
This morning I found many orders re-generated and executed (perhaps 4, each of 3 legs). So I had trades execute upon NT launch, that had been cancelled last night.
In my Log I see 33-34 "Injected execution from log:Execution=..." lines. These are under the Category Order. They all began immediately after "Session Break" and before "Automated trading enabled". They took 4 seconds to do.
I appears that these could be the new orders that triggered at the opening. Could this be a bug in the latest version? Is there something more I should do to make certain that orders aren't lingering overnight, to fire off upon launching the next session of NT?
Brian1
Comment