Coordinating Position Locks Across Concurrent VeighNa Strategies

Summary

This short VeighNa forum exchange discusses running multiple strategies on the same instrument when one strategy places orders with position locking enabled. The question asks whether other strategies sharing the same PositionHolding object also need to use locking. The reply says they do, because inconsistent locking behavior can cause conflicts when strategies share that position state.

The exchange gives a concise operational warning about coordinating order behavior across concurrent strategies. It does not describe the locking mechanism in detail, show code, or provide an example of a resulting conflict. Nor does it discuss how to isolate strategy positions or manage portfolio-level risk. Its scope is narrow: when strategies share a position-holding object, the reply recommends consistent use of locking to avoid interference between them.

Key ideas

• The discussion concerns concurrent strategies trading the same instrument through shared position state.
• The reply recommends that all strategies use position locking consistently when they share a PositionHolding object.
• The stated reason is to avoid conflicts between strategies.
• The exchange provides no implementation example or detailed explanation of the locking mechanism.

Tags

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