MT5 Stop Limit Orders: Trigger Price Versus Limit Price
MT5 stop limit orders involve two price conditions. One activates the next instruction; the other defines the limit order placed after activation. Confusing those conditions can leave you expecting a completed transaction when the account actually holds an unfilled order. The distinction matters even if both price fields look familiar.
This guide explains the sequence and offers a paper worksheet for reading the ticket. It is not a recommendation about where to enter a market. Confirm the supported order types and restrictions for your exact symbol with your broker. A feature described in platform help is not proof that every account offers it on identical terms.
What the two price fields represent
MetaQuotes’ official order definitions describe a stop limit as a conditional step that places a limit order. For a buy stop limit, the relevant Ask reaches the activation level before a buy limit is placed at the specified stop-limit price. For a sell stop limit, the corresponding condition uses Bid before placing a sell limit. Exchange instruments can have different trigger conventions.
The practical consequence is simple: activation and execution are separate events. Your worksheet should have one line for each. Do not replace the second line with a tick marked “done” merely because the first condition occurred. You still need the actual order status and execution record to establish what happened.
MT5 stop limit orders are a sequence
Think of the process as a set of questions rather than a predicted market path. Has the original instruction been accepted? Has its activation condition occurred? Was the resulting limit instruction placed? Has that instruction received any execution? Is any quantity still pending? The answers can differ, and each deserves a separate piece of evidence.
The visual shape of a chart does not settle all those questions. A chart can show one price series while the relevant order condition uses another. A screenshot also may omit the exact time, server or symbol. When investigating a discrepancy, begin with the recorded instruction and broker documentation rather than estimating the event from a candle.
A fictional buy-side example
Imagine an entirely fictional instrument with an Ask of 100. A paper exercise sets an activation level at 105 and a buy-limit level at 103. The numbers illustrate the distinction only; they are not a trade setup. If the documented activation condition occurs at 105, the next instruction is a buy limit at 103. That does not mean a purchase has already been completed at either number.
Now imagine the price never comes back to a level where the resulting limit instruction can execute. The intended entry may remain unfilled. Your notes should say “activated, limit instruction awaiting execution” if that is what the records establish. They should not say “entered at the trigger” simply because 105 appeared on the screen.
Alternatively, the resulting instruction might receive an execution consistent with its conditions. Establish that from the actual execution record. Do not manufacture a hypothetical fill to complete a spreadsheet. If your exercise omits execution rules, liquidity and account restrictions, label those elements unknown. That makes the example useful without pretending to simulate a broker.
A fictional sell-side example
For the opposite direction, imagine a fictional Bid of 100, an activation level at 95 and a sell-limit level at 97. Again, these are bookkeeping numbers with no market forecast. Activation leads to a sell-limit instruction at the specified level. The subsequent instruction still needs to be evaluated on its own status and conditions.
Write out the intended sequence in words before drawing it. This is a useful error check because arrows can hide assumptions. “If the activation condition occurs, place the specified limit instruction” describes the mechanism. “Sell immediately when the first price is touched” describes a different expectation. Keep those sentences separate when reviewing a ticket.
Read the exact symbol specification
Open the contract information for the same symbol shown in the ticket. Retain any suffix in its name. Note the account and server, because a screenshot from another broker or a general tutorial may not describe your configuration. Ask which pending order types are permitted and what minimum distance, session or expiry conditions apply.
Use the platform’s Market Watch documentation as a navigation reference, then confirm the values supplied for your account. Do not assume that a tutorial’s price precision or quantity increment fits a different contract. A copied example can look plausible while still containing invalid fields.
A worksheet for MT5 stop limit orders
| Record | Question to answer |
|---|---|
| Exact symbol and account | Which configuration does this instruction belong to? |
| Direction and order type | Is the ticket a buy or sell stop limit? |
| Activation price | Which documented condition places the next order? |
| Limit price | What condition applies to the resulting limit instruction? |
| Quantity and expiry | How much is requested, and how long may it remain pending? |
| Recorded status | What actually happened, rather than what was expected? |
Add a final column for the evidence behind each answer. The order ticket supports the submitted fields; official documentation supports the mechanism; broker records support the observed outcome. A marketing page usually cannot establish all three. Keeping those evidence types separate makes later questions more precise.
Inspect pending quantity before sending another instruction
An unfilled instruction can be easy to overlook if you focus only on open positions. Before concluding that nothing remains, inspect the pending-order record as well. Ask what quantity is still outstanding and whether the instruction remains active. Do not interpret an empty position list as confirmation that every earlier instruction has disappeared.
If the record is unclear, avoid treating a replacement instruction as a harmless duplicate. Clarify the existing status first. Your support request should identify the original ticket and ask what remains pending. This is a recordkeeping precaution, not a recommendation to cancel, enter or exit a position at a particular market level.
Expiry and cancellation are separate questions
Document the expiry selection before submitting a demo instruction. Ask what happens to the original conditional instruction and any resulting limit instruction when the relevant expiry condition occurs. The answer must match the order type and broker configuration. Do not generalize from an unrelated instrument or a screenshot showing only a simplified ticket.
Similarly, confirm a cancellation from the recorded response and updated order status. An attempted action and a completed action are different entries in a worksheet. If you lose connectivity, do not assume the last visible screen tells you the final server state. Reconcile the record through the broker’s supported process before drawing a conclusion.
How to investigate an unexpected result
Gather the ticket number, exact symbol, account environment and timestamps. State what you expected and what the records show in separate sentences. If you refer to a chart, include its price source and displayed time basis. Remove passwords, access tokens and unnecessary personal information before sharing screenshots with support.
Ask support which condition was evaluated and which instruction was subsequently placed. Request a reference to the applicable order rules. Avoid framing the question as an accusation based solely on a chart image. A useful explanation connects the submitted fields, relevant price condition and recorded status without promising that future instructions will execute the same way.
Frequently asked questions
Does the activation price guarantee a fill?
No. MT5 stop limit orders use activation to place the subsequent limit instruction. A completed transaction needs separate evidence. The distinction is the core reason to record two price fields and two stages rather than describing the whole process as one event.
Can a tutorial tell me which values to use?
A tutorial can explain field meanings. It cannot establish a suitable entry level or your account’s current restrictions. Check the precise symbol documentation, and keep fictional examples labelled as examples. This guide provides no recommended prices or quantities.
Is a demo outcome proof of live execution?
No. A demo exercise can help you understand the interface and record sequence. It does not establish future liquidity, execution, costs or live account treatment. Retain the environment label in every note so that an observation is not later presented as live trading evidence.
Sources and editorial scope
By Best Forex Brokers Editorial. This explanation uses official platform documentation and original paper examples. We do not claim to have executed these examples with a broker. Our editorial methodology describes the site’s evidence standards.
Best Forex Brokers may earn commissions from qualifying referral links elsewhere on this site. This guide contains no broker referral recommendation; platform references are informational.
This is not financial advice or investment advice. Leveraged forex and CFDs can cause substantial losses. Product availability, account rules and legal protections depend on your jurisdiction and contracting entity.
