The order status starts out empty (zero length string) while NT is waiting for the confirm dialog to be answered.
It seems to work when the order is accepted via the confirm dialog (goes from empty status string to pending to accepted etc).
The problem is when the order is canceled via the confirm dialog. In this case, the order status remains an emtpy string instead of going to the cancel or rejected state. This means that the TS side has no way of knowing what the current state of the order is and can not clean up and get ready for the next order. The Ninja side appears to clean up fine, and correctly errors any further order modifications.
The same code works perfectly when not using confirm orders, but I am trying to add the option to turn confirm orders on.
This is happening with the latest version of 6.5 and with the ZenFire feed.
Comment