[Canonical HTML article](https://algoway.trade/blog/mt5-directional-aggregate-volume-limit.html)

# **MT5 Volume Limits: Why a Valid Lot Size Can Be Rejected**

Published November 19, 2026

![Separate buy and sell capacity columns with open and pending volume](https://algoway.trade/static/img/blog-img/mt5-directional-aggregate-volume-limit.jpg)

A 0.50-lot entry can fit the broker's lot step and still be too large. MT5 distinguishes the size of one order from the combined volume already committed in the same direction. The second check is easy to miss when several strategies share an account.

For automated trading, this is an account-state problem as well as a sizing problem. In an AlgoWay workflow, use the [MT5 orders, deals and positions guide](https://algoway.trade/blog/mt5-orders-deals-positions-history.html) to separate working instructions from completed executions before retrying. A correctly calculated new size does not tell you how much capacity existing orders have already used.

## Four volume checks, not one

MetaQuotes documents four separate symbol properties: minimum deal volume, maximum deal volume, volume step and a directional aggregate limit. The first three constrain an individual request. The last combines open-position volume with pending-order volume on the same side of the same symbol. These are broker-symbol rules, so use the specification for the actual instrument and account. See the [official permitted-volume guide](https://www.mql5.com/en/book/automation/symbols/symbols_volume).

The public MQL5 names are `SYMBOL_VOLUME_MIN`, `SYMBOL_VOLUME_MAX`, `SYMBOL_VOLUME_STEP` and `SYMBOL_VOLUME_LIMIT`. They are documented platform properties, not four names for the same ceiling. Rounding a request to a valid step does not create room under the aggregate limit.

## A valid half-lot request that does not fit

Consider an illustrative symbol with a 0.10-lot minimum, a 0.10-lot step, a 3.00-lot per-deal maximum and a 4.00-lot directional limit. These numbers are invented for arithmetic, not a broker specification.

- Open buy volume: 2.40 lots.

- Remaining buy pending-order volume: 1.20 lots.

- Buy-side total already committed: 3.60 lots.

- Proposed additional Buy Limit: 0.50 lots.

The new request passes the minimum, step and individual maximum checks. But 2.40 + 1.20 + 0.50 = 4.10 lots, exceeding the directional limit by 0.10. The arithmetic leaves 0.40 lots of buy-side capacity at this snapshot. That is a capacity calculation, not a recommendation to resize the trade: changing size also changes the strategy's intended exposure.

Splitting the extra 0.50 into five 0.10-lot orders cannot solve this aggregate constraint. The total remains 4.10. A ceiling does not grow taller because the furniture arrives in smaller boxes.

## Keep the two directions separate

The [symbol-properties reference](https://www.mql5.com/en/docs/constants/environment_state/marketinfoconstants) defines the limit by direction. Its example allows buy exposure at the ceiling alongside a sell pending order at that ceiling, while another buy pending order would exceed the buy-side allowance. Do not subtract a sell pending order from the buy total as though it had already offset a position.

In the worked example, a separate 0.80-lot Sell Limit does not turn 3.60 lots of committed buy volume into 2.80. Maintain distinct buy and sell inventories. This calculation describes directional capacity for additional exposure; it is not a universal formula for closing or reversing a position. For those actions, first establish the [account's netting or hedging behavior](https://algoway.trade/blog/mt5-netting-hedging-opposite-trades.html).

## Read the rejection before changing anything

The [MT5 trade-server return-code reference](https://www.mql5.com/en/docs/constants/errorswarnings/enum_trade_return_codes) distinguishes `10014` (invalid request volume), `10034` (symbol order/position volume limit), `10033` (pending-order count limit) and `10019` (insufficient money). Save the actual server result and broker comment. More free margin does not, by itself, answer a volume-limit rejection.

For a volume-limit diagnosis, record the requested symbol, side and volume; its current specification; open positions; and remaining active pending volume. Include relevant activity from other strategies and manual trading on the same account. Counting only the orders created by the bot that failed can hide the volume that matters.

## Recalculate after confirmed changes

Suppose you decide to cancel the 1.20-lot buy pending order in the example. If cancellation is confirmed with no fill, the buy total falls to 2.40, leaving 1.60 lots before any new order. If it fills first, the volume may have moved from pending orders into the position instead. The disappearance of a pending row is not proof that capacity became free.

When changing an existing pending order's size, follow the [cancel-and-replace workflow](https://algoway.trade/blog/mt5-pending-order-change-volume.html) and reconcile the outcome before recalculating. If several bots can submit at once, treat each capacity calculation as a snapshot: another accepted order can consume the same room before your request arrives.

A useful demo check has two parts: submit a size that fits by itself but exceeds the combined ceiling, then reduce confirmed outstanding exposure and repeat the calculation. Keep the server responses with the before-and-after inventory. This is a proposed verification procedure, not a test performed for this article. The goal is to explain the rejection with the account's actual commitments, rather than repeatedly rounding a number that was already valid.
