MT5 error 10024: diagnose requests sent too frequently
When a trade request returns 10024, start by finding the sequence that triggered it. The server reports that requests were sent too frequently. The useful question is which logical action produced those requests. Compare your application's record with the resulting order and deal history before trying to send the action again.
Steps to check
- Collect a short window around the first rejection. Write down the broker symbol, requested action, time and return code. Group records that correspond to the same trade idea or position, so unrelated chart activity does not hide the repeated request.
- Check whether the automation submits again on every tick while the previous request is unresolved. If several charts or processes manage the same position, identify which one owns the operation and which ones should only observe the outcome.
- Compare the request with open orders, current positions and recent deal history. One attempt may already have taken effect while another response was delayed. Confirm the current state before deciding whether the operation still needs a new request.
- On demo, wait for a definitive response for each outstanding action and observe the next state transition. Use a bounded pause when the broker reports excessive requests. Stop the trial when the state remains ambiguous and collect the log for review.
Worked example
In a hypothetical demo, two chart instances both try to update the same position after a price change. The first modification appears in the history and the second returns 10024. The position already has the intended stop, so the duplicate request has no remaining work. The log and the final position together explain the outcome.
Frequently asked questions
Is there one safe number of requests per second?
Use the broker's rules for the exact account and action. The retcode identifies a frequency rejection. It does not specify a common rate limit that applies everywhere.
Does a rejection mean every earlier request failed?
Earlier operations may have succeeded independently. Inspect the current order and position state and compare it with the intended change before sending another operation.
What should I save for support?
Save the request type, return code, broker symbol and relevant timestamps, plus the resulting order or deal status. Remove personal and account information from any shared excerpt.
Related guides
Related video
Related MT5 troubleshooting example: invalid stops (10016)