Order Flow Limits in VeighNa: Orders Allowed per Time Window

Summary

This short forum exchange explains an order flow limit as a cap on how many order submissions may be made during a specified time window. A reply clarifies that the framework clears or resets the count after a configured number of seconds, and that the limit applies to calls to the order submission function. It points readers toward the source code for the relevant settings and behavior.

The discussion is useful for understanding a basic execution safeguard: rate limits constrain order traffic over time, which can help keep an automated strategy within a gateway or framework’s submission rules. It does not define the default window or cap, explain whether rejected or canceled orders count, or describe behavior across multiple strategies and connections. Those details depend on the implementation and configuration, so the forum answer is a starting point rather than a complete operational specification.

Key ideas

• An order flow limit caps order submissions within a configured time window.
• The framework resets the count after a configured number of seconds.
• The described limit applies to calls to the order submission function.
• The exchange does not specify defaults or how cancellations and multiple strategies are counted.

Tags

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