Error 4752 — Trading Disabled

OrderSend failed. Error code: 4752 (autotrading disabled by client/server)

When you see error 4752 in MetaTrader 5, it usually has nothing to do with your EA’s code. This message means that algo-trading is simply turned off. Many beginners panic thinking something is broken in the robot, but in reality MT5 is just protecting you from letting programs place trades without permission. If the AutoTrading switch at the top of your platform is red, your Expert Advisor will always fail with “Trading Disabled,” no matter how perfect the code is.

The fix is straightforward, but you need to check several places. First, look at the toolbar in MT5: there is a button called AutoTrading (sometimes shown as “AlgoTrading” with a small play/stop icon). If it is red, click it once. It should turn green. This is the global on/off switch for all robots. Second, right-click on the chart where your EA is attached, go to Expert Advisors → Properties, and make sure the option “Allow algorithmic trading” is checked. Without this, even if the global button is green, the specific EA will not trade. Third, open MT5 menu Tools → Options → Expert Advisors and confirm that “Allow AlgoTrading” is enabled for your whole terminal. Some users accidentally disable it here and then cannot understand why nothing works.

If after all of this the error still shows, then the broker itself might have restrictions on your account (for example, a read-only investor login or a blocked symbol). In that case, you need to contact support and ask if trading permissions are active. But in 90% of cases error 4752 is just because the AutoTrading button is red or the EA checkbox was forgotten. Remember: green button, correct EA settings, and permissions in Options — that’s the full checklist to get rid of error 4752.

Error 4756 — Request Rejected

OrderSend failed. Error code: 4756

Error 4756 in MetaTrader 5 appears when the server flat out rejects your order request. Unlike some minor warnings, this code means the broker never even tried to execute the order because something in the request did not match their rules. Many traders hit this error and immediately suspect the EA is “buggy,” but in reality the platform is telling you “your order parameters are not acceptable.”

The most common reason is no quotes. If the market is closed or the symbol has no fresh ticks, MT5 cannot fill your order. You might see “off quotes” in the logs, and that always translates to a rejected request. Another common reason is the filling type. Some brokers allow only IOC (Immediate or Cancel), others require FOK (Fill or Kill), and if your EA sends the wrong mode, the server will instantly reject it. Lot size is another trap: if the broker’s minimum lot is 0.10 and you send 0.01, the request gets bounced. Similarly, if the step is 0.01 and you send 0.07, some brokers will not accept it. Finally, some symbols are “view only” or disabled for trading, so any attempt results in 4756.

How to fix this step by step: first, open the Market Watch window and make sure your symbol is visible and receiving quotes. If it’s grey or frozen, right-click and choose Show All or Symbols to activate it. Second, check the Specifications of the symbol (right-click → Specification). Here you will see the minimum lot, step size, allowed order types, and trading sessions. Adjust your EA inputs accordingly. Third, if you suspect filling mode issues, add code in your EA to print which mode it is using, and switch to one supported by the broker. If you are not sure, test manually by opening an order through the MT5 “New Order” window — if you get rejected there too, it’s not your EA, it’s the broker’s conditions.

In short, 4756 is the platform’s way of saying “check your order parameters.” Most of the time the fix is simple: use the correct lot size, send valid stops, make sure the symbol is open and tradable, and pick the right filling mode. Once you align with the broker’s specification, the error disappears and your orders go through without issues.

Error 4014 — Invalid Stops / Function Not Allowed

OrderSend failed. Error code: 4014

Error 4014 can confuse many traders because it has two faces. When it happens after OrderSend(), it usually means invalid stop levels. In simple words: your Stop Loss or Take Profit is set incorrectly. Maybe you placed them too close to the market, or even on the wrong side of the trade. For example, if you open a Buy and set Stop Loss above entry price, MT5 will immediately block it with error 4014. Another common mistake is wrong precision: if the symbol has 2 decimals and you send 1.234 as price, MT5 rejects it as invalid.

The second face of 4014 shows up when you are using WebRequest(). In this case it means “function not allowed”. This happens if you forgot to whitelist the URL in MT5 settings. AlgoWay Expert Advisors need to connect to https://algoway.co to send and receive trade instructions. If this address is missing in your terminal options, the EA will always fail with 4014.

Here is how to fix it step by step: in MT5, go to Tools → Options → Expert Advisors. Find the section “Allow WebRequest for listed URL” and add a new line with:

https://algoway.co

Press OK and restart the terminal. Now your EA is allowed to talk to the AlgoWay servers. Remember: WebRequest is not available in the strategy tester — you must test on a live or demo chart. Also, WebRequest cannot be called from indicators, only from Expert Advisors and scripts. Once you whitelist https://algoway.co properly, the error disappears.

So the rule is simple: in trading mode 4014 means fix your SL/TP, in networking mode it means allow AlgoWay’s server in MT5 settings. One small checkbox in Options often saves you hours of confusion.

Error 10018 — Market Closed

OrderSend failed. Error code: 10018 (market closed)

Error 10018 is MetaTrader’s way of saying: “you are trying to trade when the market is not open.” This is very common with beginners who run their EA on weekends or at night without realizing that not every symbol trades 24/7. For example, Forex majors usually close on Friday evening and only reopen Sunday night, while CFDs on stocks or indices follow exchange hours. If your EA tries to send an order outside these hours, MT5 refuses and shows 10018.

The fix is not in the code but in your awareness of trading sessions. To check the schedule, right-click on the symbol in Market Watch, choose Specification, and scroll down to see the “Sessions.” This table shows exactly when the broker allows trading. If you see that the session ends at 17:00 New York time, do not expect orders to work a minute later. Many AlgoWay users forget this and keep wondering why the bot stops on weekends.

Practical steps: first, make sure your PC clock and MT5 server time are correct. Second, open the symbol specification and compare the session times with your current time zone. If you are testing, pick a symbol that is definitely open (for example, XAUUSD usually has wider hours than stock CFDs). Third, if you absolutely must run code on closed markets, add logic in your EA to check MarketInfo or SymbolInfoSessionTrade() before sending orders. This way the EA will simply wait until the market opens instead of throwing errors.

In short: 10018 means your broker is saying “come back later.” The solution is to respect trading hours, use the Specification window to learn the schedule, and design your EA to handle closed sessions gracefully.

Error 10024 — Too Many Requests

OrderSend failed. Error code: 10024 (too many requests)

Error 10024 means you are overwhelming the trading server with too many order requests in a very short time. MetaTrader 5 and brokers have built-in protection: if your EA keeps hammering the server with dozens of OrderSend() calls per second, the system will reject them all and throw this error. It is basically a polite way of saying “slow down or you will get blocked.”

Many beginners hit this error because their Expert Advisor retries immediately after a failed order without any pause. Imagine the EA sitting in a loop sending 50 orders in one second — of course the broker’s risk system shuts it down. Another typical cause is using multiple EAs on the same account, all trying to trade at once. Even if each one sends only a few orders, together they can cross the server’s rate limit.

To fix this, you need to add throttling and smarter logic. First, introduce a small delay between order attempts. Even 500–1000 milliseconds is enough to keep the server happy. Second, set a “busy” flag inside your EA: when you send an order, mark the system as busy and don’t allow another until you get a response. Third, add clear logging so you can see exactly how often orders are being fired. If you notice the EA is sending 10 orders per tick, that is a bug in the logic and needs to be fixed.

Practical tip: test your EA manually by placing trades from the MT5 “New Order” window. If one order works but the EA still throws 10024, the problem is your code spamming, not the broker. If you run several EAs, try disabling all but one to confirm if the issue is volume of requests. Remember that servers treat abnormal bursts as suspicious activity, and in extreme cases your account could even be temporarily locked.

In summary, 10024 is a warning: don’t flood the broker with requests. Add pauses, check your EA’s loops, and manage multiple advisors carefully. Once you respect the natural speed limits, your orders will flow normally again.