Troubleshooting Missing Contract Data in Scripted VeighNa Connections

Summary

This forum exchange investigates why a VeighNa trading script fails to find contracts even though the graphical Studio client receives market data. Participants explain that a strategy module may start before contract queries finish, and that simply adding a fixed delay may not solve the issue when private stream messages or account activity slow the response.

The suggested diagnostic is to wait for and inspect the contract query success log before starting dependent modules, then check the engine's contract list if the log appears but subscriptions still fail. In the reported case, scripted startup showed successful market and trading logins but lacked position and contract query confirmations; a respondent also noted that the second startup output did not show trading server information, leaving an unavailable port or incomplete connection as possible causes. This is a troubleshooting discussion rather than a complete setup guide, and it does not establish a definitive cause.

Key ideas

• A fixed startup delay may be insufficient when contract queries take longer than expected.
• Check logs for successful contract and position queries before launching dependent modules.
• If query success is logged but subscriptions still fail, inspect the engine's loaded contracts.
• Missing trading server information can point to an incomplete connection or an unavailable port.

Tags

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