Understanding Stop Orders and Direction-Dependent Triggers in VeighNa

Summary

This forum exchange clarifies how VeighNa's local stop orders are displayed and triggered. The price shown in the stop-order interface is the trigger price, rather than the price of the limit order that may be sent after triggering. A user reports that orders seemed to execute immediately despite the market not reaching the displayed price; the response explains that a short-direction stop triggers when the market is below its trigger price.

The exchange illustrates why stop-order behavior depends on order direction and why a trigger condition should be checked against the strategy engine's stop-order logic. The original poster concludes that the order type they encountered was intended for stop-loss use, not profit-taking. This is a brief, platform-specific troubleshooting discussion, not a full specification of stop-order execution or a general claim that stop orders cannot be used in other exit designs.

Key ideas

• The displayed local stop-order price is the trigger price, not necessarily the resulting order price.
• A short-direction stop triggers when the market moves below its specified trigger level.
• An apparently immediate fill can result from a trigger condition already being satisfied.
• The thread distinguishes the described stop-loss use from the poster's attempted take-profit use.

Tags

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