Normally I wouldn't care but because my strategy depends on state from actual closing of the order not requesting - I rely on NT to prevent duplicate submissions to the broker.
Initial Call:
execution='c500f1e1c866459d866e974b0eaee912' instrument='ES 12-15' account='Sim101' exchange=Default price=1905 quantity=1 marketPosition=Short orderId='551d007bc9c741e28c47a78a48cf111d' time='9/24/2015 1:00:01 PM' sod=False
Subsequent Duplicate calls (from a race condition):
execution='2c361d01426f43028bdc03071a888bcd' instrument='ES 12-15' account='Sim101' exchange=Default price=1910 quantity=1 marketPosition=Long orderId='5642ed1045e34145a6c9d323736827ee' time='9/24/2015 1:50:03 PM' sod=False
execution='76df561edf934ea1956537e06966e09e' instrument='ES 12-15' account='Sim101' exchange=Default price=1910 quantity=1 marketPosition=Long orderId='f698be18df4148149f85cb84039c1f41' time='9/24/2015 1:50:03 PM' sod=False
Do I need to manage a working state to resolve this or is this considered a bug in NT? From my perspective, I should be able to call the ExitShort() routine with no quantity and it only closes my order not reverses it regardless how many times I call it if the fromsignalName is the same.
regards,
Dave
Comment