How to Diagnose MT5 Error 10028 Request Locked
Retcode 10028 in MetaTrader 5 means the trade server reports that the request is locked for processing. It is easy to confuse with nearby codes, and a quick retry can make the situation harder to read. This guide shows how to identify what the code is telling you, how to check whether your original intent is still unresolved, and how to test safely in a demo environment without guessing at waiting times.
Steps to check
- Confirm the code and separate it from its neighbors. Code 10028 means the request is locked for processing. Code 10024 means requests were sent too frequently, and code 10029 means an order or position is frozen. Write down the exact code returned, because each one points to a different kind of problem and should not be handled with the same fix.
- Capture the identifying details of the request. Note the exact symbol, the action you attempted, the timestamp, and any order or position ticket involved. Without these details you cannot reliably match the rejection to later events, and you may end up comparing the wrong records or blaming the wrong request.
- Compare the records before deciding anything. Read the Journal entries around the timestamp, then look at pending orders, open positions and recent deals. You are checking whether the original intent is still unresolved, or whether something has already changed on the account. Only after this comparison should you decide whether any further action is needed at all.
- Do not treat acceptance as execution. MetaQuotes notes that OrderSend acceptance and actual execution are distinct, and that one request can produce several OnTradeTransaction events. So do not infer the final state from a single notification or from the initial return value alone. Keep watching the later transactions until the picture is complete.
- Test with one in-flight request per intent in a demo account. Log the request itself and every later transaction that relates to it. Wait for a definitive state before you consider another request for the same intent, and avoid repeating the request while the first one is still being processed. Do not adopt an arbitrary universal wait as a substitute for confirmed state.
- Record what you learned. Save the code, the request details, the Journal findings and the sequence of transactions together. A clear record lets you see later whether a locked request resolved on its own, whether the intent was already fulfilled, or whether it genuinely remains open and needs a deliberate, single new request.
Worked example
This is a hypothetical demo scenario. An Expert Advisor sends a request to modify a pending order, then a repeated modification returns 10028. The tester records the broker symbol, order ticket and both request times. The Journal and trade transactions show that the earlier request changed the order while the repeated request was blocked. The pending order now has the intended setting, so the tester leaves it in place. For the next demo run, the EA keeps one modification in flight per order and waits until the latest order state is known before reconsidering the change.
Frequently asked questions
Is retcode 10028 the same as 10024?
No. Code 10028 means the request is locked for processing. Code 10024 means requests were sent too frequently. Code 10029 is different again and refers to a frozen order or position. Check the exact number before choosing how to investigate.
Should I resend the request as soon as I see 10028?
Not immediately. First compare the Journal, pending orders, open positions and recent deals to see whether the original intent is still unresolved. Repeating a request without that check can create confusion about what actually happened.
How long should I wait after a locked request?
There is no universal wait that fits every case. In demo tests, keep one in-flight request for the same intent, log the request and the later transactions, and wait for a definitive state rather than relying on a fixed delay.
Related guides
Related video
Related example: automated execution through MT5