Diagnosing Strategies That Stop Receiving Market Data in VeighNa

Summary

This forum response offers a troubleshooting sequence for multiple VeighNa strategies that appear to stop responding. It recommends checking whether logs continue, adding output in tick or bar callbacks to confirm incoming data, verifying that a strategy is initialized and trading, confirming subscribed symbols, looking for exceptions, and checking whether slow work is blocking the main event thread.

It also describes a possible Windows terminal selection or edit mode that can pause visible output when VeighNa Trader is launched from a command prompt. The advice distinguishes a quiet display from a strategy that has actually stopped receiving data or processing events. These are diagnostic suggestions, not a confirmed explanation for the original report: the post supplies no logs, code, or reproduction, and the cause would depend on the user's setup.

Key ideas

• Use callback logs to determine whether ticks or bars are still reaching a strategy.
• Check strategy initialization and trading status, subscribed symbols, and market data continuity.
• Inspect exceptions and avoid lengthy operations that block the event loop.
• A Windows terminal mode can pause displayed output even while the process appears open.
• The post provides a diagnostic checklist but does not establish the cause of the reported issue.

Tags

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