Guides, manuals and platform references.
Published November 4, 2026 · View Markdown
You cannot change the volume of an existing MT5 pending order through order modification. If a Buy Limit was submitted for 0.50 lots, editing its entry price does not make it a 0.20-lot order. To replace an unfilled order with a different size, cancel the original, confirm what happened to it, and submit a new order.
This matters in automated trading because a revised signal is a new intention, while the broker still holds the old instruction. In an AlgoWay workflow, use the MT5 orders, deals and positions guide to reconcile the account before sending another entry. A changed sizing input is not evidence that an already accepted pending order changed.
MetaQuotes documents changes to the activation price, protective stop levels and expiration. Volume, fill policy and comment are excluded from ordinary pending-order modification. On desktop MT5, open the order's context menu in the Trade tab and choose the modify/delete command. An inactive modification button can also mean that the proposed parameters are invalid. See the official pending-order management instructions.
Keep three tasks separate: changing where a pending entry will activate, replacing how much that entry will trade, and reducing a position that has already opened. Only the first is a simple entry-price edit. The second requires a replacement order; the third is position management.
Suppose an unfilled 0.50-lot Buy Limit is waiting below the market. Your revised plan permits only 0.20 lots at that price. These are hypothetical quantities, not a trade recommendation.
Submitting 0.20 lots first and deleting 0.50 lots afterward creates an interval in which both instructions can exist. If both fill, the total bought can be 0.70 lots. Conversely, canceling first leaves an interval without the intended pending entry. Cancel-and-replace is a sequence of events, not a magic eraser.
MT5 distinguishes placed, partly filled, filled, canceled and expired orders, and records initial and remaining order volume. Those distinctions are documented in MetaQuotes' order properties reference. An order disappearing from the active list alone does not tell you which outcome occurred.
Consider a venue and order policy that permit partial execution. Of the original 0.50 lots, assume 0.10 has already filled and the remaining 0.40 is successfully canceled. If your intention is a total purchase of 0.20 lots for this entry, only 0.10 remains to be bought. A fresh 0.20-lot order would instead bring the total to 0.30 if filled.
If 0.30 lots have already filled, the desired total of 0.20 cannot be reached by replacing the pending entry. You now have an exposure-reduction decision. Account mode matters when managing opposite trades; consult the netting versus hedging explanation before treating a sell instruction as a universal close command.
The public MQL5 OrderSend documentation explicitly separates a successful function return from successful trade execution. A program must examine the server response and subsequent trade state. The same operational distinction is useful when reviewing a connector workflow: request sent, order accepted, order canceled and trade filled are different facts.
A practical replacement policy should record the old order reference, requested new size, confirmed fills, remaining active volume and replacement order reference. If a cancellation outcome is unknown, investigate it before treating the old order as gone. A timeout provides uncertainty, not permission to assume success.
Test the ordinary no-fill replacement and the fill-before-cancel case separately on a demo account. Also check what happens when a new signal arrives while replacement is in progress. This article describes MT5 order semantics and a reconciliation procedure; it does not assume a connector provides an atomic volume-replacement command.
The final check is simple: add the confirmed fills to any remaining intended entry volume. That total should match the revised plan. Changing the number in a settings panel is the beginning of that check, not its conclusion.