How VeighNa Local Stop Orders Trigger and Become Limit Orders

Summary

This brief forum exchange concerns stop orders in VeighNa 4.3 when running multiple processes or strategies. A user reports that stop orders for exits refresh as expected with one process and one instrument strategy, but stop orders no longer appear after opening multiple VeighNa processes and strategies. The exchange does not resolve the reported multi-process behavior.

A reply explains the local stop-order execution sequence: once the trigger price is reached, the CTA engine sends a limit order at the price limit or within the top five levels of the order book to pursue immediate execution. The main trader interface then displays the limit order status, while the stop is marked triggered and linked to its limit-order identifier. The reply recommends local stops only for sufficiently liquid contracts. This is operational guidance, not a diagnosis of the missing-stop display issue, and it provides no test results or details about process coordination.

Key ideas

• A local stop triggers a limit order rather than remaining a stop order after activation.
• The engine uses a price limit or top-five book pricing in an effort to get an immediate fill.
• The interface shows the resulting order and marks the stop as triggered.
• The reply recommends local stops for liquid contracts and does not explain the multi-process symptom.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.