Checklist · Order Execution
Order Rejection: A Broker Support Diagnostic Sheet
Investigate a rejected order using the exact response, symbol rules, account state and event history before changing settings or resending requests.
Published Updated
Published by FxTrusts, a supplier of brokerage and prop firm technology. Prepared with AI-assisted research and drafting; reviewed against the cited public sources. Examples are illustrative. Product links describe our services.
Quick answer
Start an order-rejection review with the exact request and response, then compare them with the instrument specification, account state and supported instruction types at that time. Do not guess from a generic interface message or immediately resend an uncertain request.
Capture the smallest complete evidence packet
Record the request identifier, account and symbol identifiers, side, quantity, prices, order type, lifetime and requested fill policy. Keep the raw response code and explanatory text alongside client-send and server-receive timestamps where available. Remove credentials and unnecessary personal data from the support copy. A screenshot can supplement the record, but often omits the request fields that determine whether an instruction was valid.
Check the instrument before changing account settings
Compare quantity with the minimum, step and maximum; compare prices with the tick grid and any distance restrictions. Confirm the trading session, symbol availability and supported order/filling modes. A symbol with similar text on another server can have different rules. MQL5’s symbol properties illustrate how many independent constraints exist. Altering leverage will not resolve an invalid quantity step, and increasing precision will not make an unsupported order type valid.
Check account state and permissions at the event time
Review available margin, account mode, trading permissions and any applicable position or volume limits. Use the values that existed when the request was processed, not a later balance after another trade closed. A pending order that was accepted earlier can encounter a separate check when it activates. Distinguish submission rejection, activation failure and a request that was accepted but remains unfilled.
Decide whether a retry is safe
A clear terminal rejection differs from an unknown outcome caused by a timeout. Before retrying an uncertain request, query or reconcile the source state using the original identifier where supported. If the request was invalid, change only the confirmed cause and preserve a link between attempts. If evidence remains inconsistent, escalate the packet with the expected rule and observed result. Avoid inventing a universal meaning for a numeric reject code across platforms.
A diagnostic record for an invalid quantity
This synthetic case requests 0.12 lots for a symbol whose minimum is 0.10 and step is 0.05. Under a grid starting at 0.10, valid quantities include 0.10 and 0.15, so 0.12 is invalid. The example does not supply a product-specific rejection code. The reviewer records the actual code, confirms no execution occurred and follows the authorized amendment process rather than silently rounding the customer’s instruction.
| Check | Observed value | Review result |
|---|---|---|
| Requested quantity | 0.12 lots | Preserve original request |
| Minimum and step | 0.10 minimum; 0.05 step | 0.12 is outside the declared grid |
| Order outcome | Explicit rejection in source record | Do not count as a fill |
| Next action | Obtain a valid authorized instruction | Do not silently change size |
Implementation checklist
- Preserve the exact response and request identifiers.
- Verify symbol-specific quantity, price, session and instruction constraints.
- Reconstruct account values and permissions at processing time.
- Reconcile unknown outcomes before retrying and avoid silent order changes.
Sources
These documents support the reference. Check the original publication for current requirements and the limits of its scope.
- MQL5 symbol propertieswww.mql5.com
- MQL5 account propertieswww.mql5.com
- MetaTrader 5 trading principleswww.metatrader5.com
Continue with the broader guides
Connect this reference to platform selection and the wider operating workflow.