Check the trigger first, then the execution. A stop-limit instruction contains those separate stages. A triggered or submitted label does not establish a completed sale, and the word “stop” does not remove the price boundary from the limit order that follows.
The two prices do different jobs
The trigger identifies the condition for activating the next instruction. The limit defines acceptable execution prices after activation. For a sell limit of 94, bids at 92 do not meet the stated minimum, even if the preceding trigger condition has already occurred.
Binance’s stop-limit explanation explicitly distinguishes activation from a fill. Check the current spot function you actually use: similarly named features in derivatives, margin products or another venue may have additional conditions.
A fictional move from 96 to 92
Set a teaching example with a sell trigger at 95, a limit at 94 and a quantity of two units. Assume the trigger condition is met and the resulting limit instruction is successfully submitted. Now suppose the available buyers after that rapid move only bid 92.
The second condition remains unmet because 92 is below the minimum sell price of 94. A label confirming the first stage cannot supply buyers at a higher price. This example is constructed to explain the mechanism; it is not an observed market event or a recommended arrangement of prices.
If a buyer later becomes available at 94 for half a unit, the instruction may execute only that portion under the applicable rules. Triggered, partially filled and fully filled remain different descriptions. The executed quantity is needed to tell you how much actually traded.
Equal trigger and limit prices do not guarantee execution
Setting both numbers to the same value makes the activation threshold and the execution boundary coincide. It does not ensure that sufficient matching quantity will remain at that value when the limit instruction is processed.
A gap between the values can allow a range of prices after activation, but there is no universal gap that guarantees a result for every asset and quantity. A wider acceptable range can permit a worse price; a narrower range may leave more quantity unmatched. Those consequences cannot be reduced to a single percentage suitable for everyone.
Reverse the comparison for a buy
A buy limit is a maximum rather than a minimum. Suppose a fictional buy trigger is 105 and the maximum buy price is 106. If the available asks after activation are 108, they lie beyond the limit. The trigger can be satisfied while the available sellers remain too expensive for the instruction.
Before entering the values, write two ordinary sentences: “When this condition occurs, activate a buy,” and “The most I accept per unit is this amount.” If the form does not match those sentences, recheck the side, units and selected order type. A form accepting the inputs does not prove that they express your intention.
A past limit-price touch cannot fill an inactive stage
You might see that the limit price was visited earlier and wonder why nothing traded. If the required trigger had not yet occurred, the later limit stage was not active. A historical acceptable price does not reserve an execution for an instruction activated afterwards.
Once the limit stage exists, the ordinary price-and-quantity checks become useful. Before that point, establish the trigger and submission result. An instruction that was rejected or never reached the next stage cannot be explained solely by the current order-book price.
Where to find the trigger time and filled quantity
- The complete pair, side and order type.
- The trigger condition and its recorded time zone and time.
- The resulting limit, original quantity and submission status.
- Cumulative execution and associated trade records.
- The current open state or terminal state, including any stated reason.
The official guide checked on 13 September 2026 directs app users to Conditions under Open Orders for the submission timestamp. On the website, click Submitted after activation. Look under Order History for filled or cancelled orders. Labels can vary with the interface version; check filled quantity separately from the trigger indicator.
Keep the initial condition in your private notes too. After activation, the visible limit order may be easier to find than the setting that produced it. Without the initial condition, it is tempting to combine several similarly priced orders into a story that the records do not actually support.
Know which instruction you are changing
If you decide to adjust the order, first identify whether the object is an untriggered condition or an already active limit instruction. Creating a new conditional order does not necessarily stop an existing limit order. Two live instructions can later affect the same intended quantity.
Cancellation also needs a result. Re-read the final executed quantity before calculating another sell amount; a fill may have occurred before the cancellation was processed. The cancellation guide illustrates that timing issue without assuming a particular network delay.
Record the trigger, fill price and quantity separately
A practical observation card keeps the original intention separate from the later result. Before submission, record the condition in ordinary language and describe the acceptable execution boundary. After submission, add the order ID and observed waiting state. When the condition changes, append the new observation instead of rewriting the initial settings to match what you now think you intended.
This makes several problems distinguishable: the input may not have expressed the plan, the condition may not have occurred, the limit may lack matching quantity, or the result may still be unknown. Each needs different evidence. One final screenshot often cannot show which stage first departed from your expectation.
In the two-unit example, a fill of 0.5 completes 25% of the order and leaves 1.5 unfilled. The trigger at 95 does not tell you the price received for that half unit. Read its trade record to calculate the proceeds, and use the filled quantity to establish how much of the holding was sold.
A useful statement is “trigger 95, minimum sell 94, zero executed, currently open.” Another is “half a unit executed, remainder cancelled.” Those statements preserve the two-stage mechanism and the final quantity. They are much more useful for the next decision than treating the feature name as a promise of a completed exit.