Diagnosing Why VeighNa Cancel-All May Not Cancel Orders

Summary

This forum response outlines a debugging process for a cancel-all issue in VeighNa. It recommends confirming that the cancellation method is reached, logging active orders, checking their statuses, and issuing individual cancellation requests for orders that are still submitting or unfilled. It also asks for strategy code, logs, and the steps that trigger cancellation so the problem can be reproduced.

The response identifies common causes such as an unmet trigger condition, no active orders, or an order status that cannot be canceled. It is operational guidance rather than a trading strategy, and it provides no evidence that the suggested procedure resolves a particular user’s case. One example shown for adding debug output calls the same method from within itself, which would recurse instead of performing cancellation; the separate example that iterates active orders is the more informative pattern. Actual behavior can also depend on the gateway and order state, so the advice should be checked against the installed VeighNa version and connection.

Key ideas

• Verify that the cancellation trigger runs and inspect the application logs.
• List active orders and check whether their statuses allow cancellation.
• The response suggests sending cancellation requests for eligible unfilled orders.
• One debug example recursively calls itself and should not be copied as written.

Tags

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