You ordered three units and only one filled. Are the other two still waiting, or has the order ended? Open the original order and check its executed quantity and status. The examples below show what remains active and how a second order can exceed your intended total.
Three ordered, one filled: are two still open?
Suppose you submitted a buy for three units and the cumulative executed quantity is one. Three minus one leaves two unexecuted units. That calculation alone does not tell you whether those two remain on the book. An open instruction, a cancelled instruction and an expired instruction can all have the same original and executed quantities.
| Original | Executed | Confirmed state | Meaning of the other two |
|---|---|---|---|
| 3 | 1 | Open ordinary GTC limit | They may still execute |
| 3 | 1 | Cancelled | They no longer wait through this order |
| 3 | 1 | Ended under immediate-execution rules | Check the reported terminal result |
These are fictional records. The first row still has an active remainder; the second has none, even though both show two units unfilled. Use the status to tell them apart.
One order can produce several trade rows
An order describes what was requested. A fill records an execution against that request. If the first fill is 0.4 units and the second is 0.6, the total is one. Two rows do not necessarily mean you pressed Buy twice, and the latest row of 0.6 is not the cumulative total.
Use the order ID, complete pair and correct account scope to group the rows. Check date filters, pagination and time zones before concluding that a fill is missing. A record outside the current display range can explain why visible rows do not yet add up to the cumulative field.
For another example, fills of 0.35, 0.25 and 0.40 total one unit. If the screen shows only the last two, their sum is 0.65. The missing 0.35 may be on an earlier page. Find that row and check its order ID before changing your total.
The official Binance status definitions distinguish partial from complete execution. Those definitions explain the labels; the numerical result still comes from the records for your own order.
How a second attempt exceeds the original target
Return to the three-unit target. One has executed and two remain open. If you submit another order for three, then both orders eventually complete, you can end up with six. The extra quantity comes from two valid instructions, not necessarily from a duplicated history entry.
Submitting only the apparent two-unit gap can also exceed the target. If the original two units are still active and both remainders execute, the total becomes five. A subtraction does not cancel an instruction. First decide what happens to the original remainder, then calculate any new quantity from a confirmed result.
This distinction is especially useful when a mobile page appears slow to update. An unchanged row is not proof that no new execution occurred. Refresh or query the official records for the same order rather than using a second full-sized submission as a way to test whether the first worked.
Keep it, stop it or make a new plan
Keeping the remainder means you still want it to execute under its existing conditions. Closing the page does not itself end the instruction. Later trades can occur while you are no longer watching, so an open remainder deserves to remain part of your current plan.
Stopping it requires a confirmed cancellation result. An additional fill may occur before cancellation is processed. If you first saw one unit, but the final cumulative result is 1.3, the stopped remainder is 1.7. The 1.3 already traded does not disappear when the remainder ends.
The cancellation timeline explains that interval in more detail. After the original state is clear, a new plan might keep the existing quantity, change the target or use different conditions. There is no obligation to complete an old quantity merely because it was once entered into a form.
A small remainder is not automatically a valid new order
You may find that the unexecuted difference is too small to submit independently under current minimum-amount or increment rules. A remainder belonging to an existing order and a newly submitted instruction are not the same operation. Identify which one you are dealing with before applying the relevant checks.
Do not automatically increase the quantity just to cross a minimum. Doing so changes the amount you are choosing to trade. If you decide to make a new order, check its current pair-specific inputs; the quantity-increment guide shows why an amount can look sufficient while another input still fails.
Reconcile execution before interpreting the wallet
A wallet balance can change because of fees, other transactions and the distinction between available and locked funds. It is not a substitute for the cumulative execution field of one order. First establish what that instruction traded; then investigate how those trades appear in the balance records.
Check the units too. Buying three units of a base asset differs from spending three units of the quote asset. Some interfaces accept an amount and then display the resulting asset quantity elsewhere. Subtracting values in different units produces a plausible-looking but meaningless remainder.
Record the filled quantity and active remainder
“Original three, final execution 1.3, original order cancelled, no active remainder” is clearer than “only a little arrived.” For an order still waiting, write “one executed, two still open at the time checked.” If there are several orders, give each its own line before adding totals.
When the final state cannot be established, keep that uncertainty explicit. Do not replace an unknown with zero execution. Save the order ID, time, original quantity, latest status and any contradictory records for official support. Resolving those facts first makes the next decision simpler and prevents new instructions from obscuring what the original one did.