When an order says EXPIRED, read its executed quantity before repeating the request. Expiry identifies a terminal outcome under applicable rules. The label alone proves neither a complete fill nor an absence of trades. You need the status and the quantity together.
Separate “still active?” from “how much traded?”
Those questions describe different aspects of the same instruction. Suppose an original quantity of three has one unit executed and a final status of EXPIRED. No two-unit remainder continues waiting through that order, but the executed unit remains a trade.
| Status | Executed quantity | What the record establishes |
|---|---|---|
| EXPIRED | 0 | The order ended with no cumulative execution in this record |
| EXPIRED | 1 | The order ended after one unit traded |
| FILLED | Reconcile with the complete order quantity | The instruction completed |
The quantities are fictional examples, not promises about the exact labels shown in every interface. Save the raw status and numerical fields for the actual order. If they appear inconsistent, verify that you are comparing the same ID, pair and account scope.
Expiry need not mean it waited a long time
Some execution conditions require immediate processing. An instruction can execute an available portion and then end the rest, or require complete immediate execution and finish with none when that condition cannot be met. Such outcomes can occur quickly.
The official Binance enum reference includes order-type rules and exchange actions in its explanation of EXPIRED. The word by itself therefore cannot identify one specific cause. Read the order type, time in force and any returned reason information.
An expired order may have filled one of three units
Imagine an instruction for three units that attempts immediately available execution and does not retain the remainder. One eligible unit executes; the other two end. The order leaving the open list and the account showing one executed unit are consistent with each other.
If you interpret disappearance as “nothing happened” and submit another three, a complete new fill brings the total to four. Write the old result first: original three, executed one, original instruction ended. Only then consider whether the target remains three and whether any further quantity is wanted.
The different remainder arrangements are compared in the GTC, IOC and FOK exercise. Its fixed numbers isolate the timing condition; actual records still determine what happened to your own instruction.
Keep EXPIRED_IN_MATCH intact
This separate status relates to self-trade prevention. It should not be shortened to a generic network timeout or treated as an ordinary expiry without the rest of the label. Preserve the complete status, pair, time and any associated prevention information.
An ordinary user interface may not display every technical field. If the reason remains unclear, ask official support to interpret the specific record. Repeated submission does not explain the restriction and can create more instructions that need reconciliation.
If the record includes a prevented quantity, keep it separate from executed quantity. The prevented match did not become a trade. Use the associated order IDs and the recorded STP mode when asking support what happened; the word EXPIRED alone is not enough to identify that event.
For example, a new buy could meet a sell already placed by the same account. The recorded STP mode determines how that attempted self-match is handled. The official STP guide also covers accounts in the same trade group. Check the actual record rather than assuming every mode ends the same side.
A timeout message is not the order’s final status
A timeout describes a missing or delayed response to you. An order status describes the instruction recorded by the platform. Both may appear during one sequence, but they are not synonyms. If you first receive a network message and later retrieve an expired order, record both facts separately.
When only a timeout is known, do not assign EXPIRED in advance. Find the relevant order record, checking the pair, date range and account. An unknown result cannot safely be rewritten as zero execution merely because the interface did not immediately show a confirmation.
Move from the open list to historical records
The open list is intended for active instructions, so an ended order leaving that view is unsurprising. Order History helps establish original parameters and the final state. Trade records help establish actual execution. Use both for the same order.
Before concluding that a record disappeared, inspect date filters, pagination and time zones. One instruction may have several fills, only some of which fit the current view. Do not mix another pair with a similar base-asset name into the sum.
If an export contains both an event type and an order status, keep the field names. An event describes an update; a status describes the instruction’s state at the reported point. Two English labels appearing near each other in a table are not automatically interchangeable.
A user cancellation has a different reason
Both cancellation and expiry may leave no active remainder, but their recorded reasons differ. A user-requested cancellation also needs confirmation that the request was processed. The already executed portion remains relevant in either case.
If you are investigating a cancel click followed by uncertain feedback, use the cancellation-result checklist. Treating every ended order as the same event discards timing evidence that may explain the discrepancy.
End the investigation with an explicit record
A concise note might read: “Spot pair X, original three, executed one, final EXPIRED; checked associated fills; no open remainder found.” If the cause is still unclear, add “reason awaiting official clarification” rather than inventing maintenance, liquidity or balance explanations.
Preserve original event dates when updating your interpretation. Today’s document review does not change when a historical order occurred. Once the factual record is clear, decide whether any new instruction is necessary. If the records still conflict, resolve that conflict through official support instead of using another trade to cover an uncertain result.