Did My Order Cancel? Confirmation and Fill Checklist
Separate a cancellation acknowledgement from the final order state and preserve any fills that occurred before the remaining amount was canceled.
Put the cancel request and final event on separate lines
Cancellation has a timeline. The moment you request it, the response you receive and the final state of the order can be different events. A fill recorded around that period does not automatically contradict the request. Start by putting the request and final evidence on separate lines, each tied to the same order identifier and its venue.
Read the exchange-specific meaning of an acknowledgement
Read what the response actually confirms. OKX documentation distinguishes acceptance of a cancel request from the final order state. Coinbase Exchange documents a different cancellation response contract and a race caveat. Preserve the original acknowledgement wording in the worksheet, then record the evidence that establishes the final outcome. A general success label without this context can conceal an unresolved state.
Preserve executions that already happened
Executions that already occurred remain part of the record when a remaining amount is canceled. Keep the own fill reference alongside the final status instead of deleting the execution because the order later stopped resting. The hypothetical example below separates the filled portion from the canceled remainder. It illustrates a completed record, rather than a prediction about when a live cancellation will arrive.
Treat cancel-replace as more than one outcome
A replacement instruction introduces another outcome to track. Cancellation of an old order and acceptance of a new one are separate components, which Binance documents explicitly for cancel-replace. Give a replacement its own identifier and evidence reference when one exists. A single combined note such as changed order would make it harder to explain a partial success or an unresolved component later.
Complete the final-evidence checklist
Use the CSV to preserve request time, acknowledgement meaning, final state and any own fill evidence. Leave a missing final result as unknown. The TXT questions are a shorter review of the same trail. These downloads organize records already available to you; they do not send a cancellation, request an account connection or decide what should happen to a live order.
Documented venue distinctions
These statements apply to the named provider and documented product. They do not imply identical rules elsewhere.
- OKX cancellation success acknowledges the request; final order state must be distinguished from that acknowledgement. Official reference.
- Coinbase Exchange documents a successful cancellation response and its own race caveat. Official reference.
- Binance cancellation responses expose status and executed quantity; cancel-replace has separate component outcomes. Official reference.
Hypothetical case
Hypothetical request: 1.0 units. Own fills total 0.4, and the final record is canceled. The filled 0.4 remains an execution; the remaining 0.6 was canceled. An acknowledgement followed by FILLED is not recorded as a successful cancellation.
Six questions for your record
- When was cancellation requested?
- Did the response acknowledge a request or confirm a result?
- What final status is recorded for the same order?
- What own fills remain in the record?
- Was a replacement order a separate action?
- Which final evidence is still missing?
Keep your own record
The CSV contains column headings only. The TXT contains the review questions and blank note spaces. Keep original evidence separately, preserve identifiers as text and leave missing facts unknown. Neither file sends data or performs an account check.