How to Fix MT5 Error 4752: Algo Trading Disabled in MetaTrader 5

MT5 Error 4752 means MetaTrader 5 is blocking Expert Advisor trading. In an AlgoWay setup, the TradingView alert may be sent correctly, the AlgoWay webhook may receive the JSON correctly, and the AlgoWayWS-MT5 EA may receive the command correctly — but MetaTrader 5 refuses the final order because automated trading is disabled.

This is why Error 4752 often appears during TradingView to MT5 automation, MetaTrader 5 webhook execution, or AlgoWayWS-MT5 EA setup. The error is usually not caused by TradingView and not caused by the webhook itself. It is usually caused by one of the MT5 permission switches that controls whether Expert Advisors are allowed to trade.

The typical execution route is:

TradingView alert → AlgoWay webhook → AlgoWayWS-MT5 EA → MetaTrader 5 order request → Error 4752

Last updated: 2026-05-12 • Author: AlgoWay

Why This Error Matters in TradingView to MT5 Automation

Error 4752 is one of the most confusing problems in a TradingView to MetaTrader 5 automation setup because the signal chain can look successful until the very last step. The TradingView webhook alert can fire correctly. AlgoWay can receive a valid JSON payload. The webhook route can be active. AlgoWayWS-MT5 EA can be connected. Still, the MT5 terminal can reject the order because the terminal, chart, account, or broker does not allow automated trading.

That makes this problem different from a broken TradingView alert, wrong webhook URL, invalid JSON, or AlgoWay routing issue. If the AlgoWay webhook logs show the request and MT5 Experts logs show Error 4752, the next work is inside MetaTrader 5 permissions, not inside Pine Script. This distinction is important for SEO and for troubleshooting because many users search for phrases such as TradingView webhook not opening MT5 trade, MT5 EA not trading, AutoTrading disabled by client terminal, Algo Trading disabled MT5, and AlgoWay MT5 Error 4752.

In other words, Error 4752 is a permission-layer failure. The automation path is alive enough to reach the EA, but MetaTrader 5 refuses to let the Expert Advisor place the trade. The correct fix is to enable and verify all algorithmic trading permissions before changing the TradingView alert message, strategy placeholders, order size, symbol mapping, or webhook JSON.

Quick Answer

Error 4752 is commonly shown as:

OrderSend failed. Error code: 4752
Trading by Expert Advisors prohibited
AutoTrading disabled by client terminal
ERR_TRADE_DISABLED

To fix it, check these points first:

1. Enable Algo Trading or AutoTrading on the MT5 toolbar.
2. Open Tools → Options → Expert Advisors and allow algorithmic trading.
3. Open the EA settings on the chart and allow the EA to trade.
4. Enable DLL imports if the current AlgoWayWS-MT5 setup requires it.
5. Check the MT5 Experts and Journal tabs for the exact rejection message.
6. If everything is enabled locally, check whether the broker or account type blocks automated trading.

What MT5 Error 4752 Means

Error 4752 is the MetaTrader/MQL5 error commonly known as ERR_TRADE_DISABLED. In practical terms, MT5 is saying: this Expert Advisor is not allowed to place trades right now.

This does not necessarily mean that the EA is broken. It means that trade execution by an EA is prohibited at the terminal, chart, account, broker, or environment level.

The Main Causes of MT5 Error 4752

In real AlgoWay support cases, Error 4752 usually comes from one of several permission switches. The important point is that MetaTrader 5 has more than one place where automated trading can be blocked. One enabled switch does not guarantee the whole EA execution path is allowed.

• Global Algo Trading is disabled in the MT5 toolbar, so every EA is blocked.
• Algorithmic trading is disabled in Tools → Options → Expert Advisors.
• The specific EA is not allowed to trade in the chart properties.
• DLL imports are blocked when the current EA setup requires external library access.
• The account is read-only, investor login is used, or the broker account cannot trade.
• The broker or server restricts Expert Advisor trading for the account type, symbol, or session.
• A VPS migration, profile switch, account switch, or terminal restart changed MT5 permissions after the EA was already working.

This is why a proper Error 4752 fix should be methodical. Do not only click the toolbar button and assume the issue is solved. Check the global terminal switch, the Expert Advisors options page, the EA chart permissions, the account login type, and the broker/server logs. AlgoWay can deliver the command, but MT5 still controls whether the EA may trade.

Diagnostic Order: Webhook First, MT5 Permission Second

When a user says “TradingView alert reached AlgoWay but no MT5 order opened,” check the layers in the correct order. First confirm whether the webhook side is working. Then confirm whether the EA side receives the command. Only after that check the MetaTrader 5 execution permission.

1. AlgoWay Webhook Logs: confirm that the TradingView alert payload arrived.
2. Payload format: confirm that JSON is valid and the route is correct.
3. EA connection: confirm that AlgoWayWS-MT5 is connected and reading tasks.
4. MT5 Experts tab: confirm whether Error 4752 appears when the EA tries to execute.
5. MT5 permissions: enable the toolbar, Options, EA properties, and required DLL access.
6. Broker/account status: confirm manual trading and EA trading are allowed.

This workflow prevents unnecessary changes. If AlgoWay never received the webhook, the issue is not Error 4752. If AlgoWay received the webhook and MT5 says automated trading is prohibited, the issue is not the TradingView strategy. It is the MT5 permission layer.

Why Error 4752 Appears with TradingView Alerts

TradingView does not place the final MT5 order. TradingView sends an alert. AlgoWay receives and processes that alert. The MT5 Expert Advisor performs the actual execution inside MetaTrader 5.

That means a signal can pass the first parts of the chain and still fail at the final MT5 permission layer:

Layer	Status	What it means
TradingView alert	Sent	The alert fired and tried to send a webhook.
AlgoWay webhook	Received	AlgoWay received the JSON signal.
AlgoWayWS-MT5 EA	Signal received	The EA got the command from AlgoWay.
MetaTrader 5 order execution	Rejected	MT5 blocks automated trading and returns Error 4752.

This is why the user may see successful webhook logs but no trade in MT5.

Fix 1. Enable Algo Trading on the MT5 Toolbar

The first check is the global MT5 automation switch.

1. Look at the top toolbar in MetaTrader 5.
2. Find Algo Trading or AutoTrading.
3. Enable it.
4. Confirm that the button shows the enabled state.

If this global switch is disabled, every Expert Advisor in the terminal is blocked from trading, including AlgoWayWS-MT5.

Fix 2. Allow Algorithmic Trading in MT5 Options

The second check is the terminal-level Expert Advisor settings.

MT5 → Tools → Options → Expert Advisors

Check the following:

• Allow algorithmic trading is enabled.
• Settings that disable algo trading after account change, profile change, or chart symbol change are reviewed.
• If the current AlgoWayWS-MT5 EA setup requires DLL access, Allow DLL imports is enabled.

After changing these settings, restart the EA or reattach it to the chart and test again.

Fix 3. Allow Trading for the Specific AlgoWayWS-MT5 EA

MT5 can allow algo trading globally while still blocking a specific EA on a specific chart. This is one of the most common causes of Error 4752.

1. Open the chart where AlgoWayWS-MT5 EA is attached.
2. Press F7 or open Expert Advisors → Properties.
3. Open the Common tab.
4. Enable EA trading permissions.
5. Enable DLL imports if required by the current AlgoWayWS-MT5 setup.

If the EA is not allowed to trade from its own chart properties, MT5 can still return 4752 even when the toolbar button is enabled.

Fix 4. Check Whether the Broker or Account Blocks EA Trading

If all local MT5 settings are enabled and Error 4752 still appears, check the broker/account side.

Possible broker-side causes:

• you are logged in with an investor/read-only password;
• the account is not allowed to trade;
• the broker disabled automated trading on this account type;
• the symbol is not tradable on this account;
• the account is connected to a VPS or migration state that changed EA permissions.

To confirm, try placing a small manual trade on the same symbol. If manual trading also fails, the issue is not AlgoWay. If manual trading works but EA trading fails, return to MT5 EA permissions and broker rules for automated trading.

Fix 5. Check MT5 Experts and Journal Logs

MetaTrader 5 logs show whether the block comes from the terminal, the EA, the account, or the trading server.

1. Open the bottom terminal panel in MT5.
2. Check the Experts tab.
3. Check the Journal tab.
4. Search for 4752, trade disabled, prohibited, or AutoTrading disabled.

Common log messages include:

Trading by Expert Advisors prohibited
AutoTrading disabled by client terminal
trade disabled
ERR_TRADE_DISABLED
OrderSend failed. Error code: 4752

How to Confirm That AlgoWay Is Not the Blocking Layer

AlgoWay has two important roles in this chain: receiving the webhook and routing the command to the MT5 connector. If those two steps are visible in logs, the remaining rejection belongs to the execution environment. This is why AlgoWay logs and MT5 logs should be read together.

Use this interpretation:

Observation	Meaning	Next action
No AlgoWay log entry	TradingView did not reach AlgoWay.	Check webhook URL, alert status, TradingView plan, and JSON delivery.
AlgoWay received invalid payload	The request arrived but cannot be parsed correctly.	Fix JSON, content type, quotes, commas, and required fields.
AlgoWay received valid payload and MT5 logs show 4752	The webhook chain works, but MetaTrader 5 blocks EA execution.	Fix MT5 algorithmic trading permissions.
MT5 accepts EA trading but broker rejects order	This is no longer Error 4752.	Check broker error, symbol, lot size, stops, market session, filling mode.

This separation is useful for users running automated trading from TradingView, Telegram signals, manual webhook alerts, or another AlgoWay source. Error 4752 is not source-specific. It can appear with any source when the final destination is MetaTrader 5 and the Expert Advisor is not allowed to trade.

What Not to Change First

When Error 4752 appears, do not immediately rewrite the Pine Script strategy, change the webhook UUID, rebuild the AlgoWay route, or replace the JSON schema. Those changes can create new problems while the real issue remains unchanged. If the error message clearly says that trading by Expert Advisors is prohibited, the first fixes are MT5 permissions and account trading permissions.

Also do not confuse a successful TradingView alert with a successful MT5 trade. A TradingView alert only proves the source event fired. AlgoWay logs prove the webhook was received and processed. The MT5 Experts and Journal tabs prove whether the terminal accepted or rejected EA execution. For Error 4752, the key evidence is in MetaTrader 5.

AlgoWayWS-MT5 Specific Checklist

Use this checklist when Error 4752 appears in the current AlgoWayWS-MT5 EA workflow:

Check	Where	Expected result
Algo Trading switch	MT5 toolbar	Enabled
Algorithmic trading permission	Tools → Options → Expert Advisors	Allowed
EA chart permissions	Chart → F7 → Common	EA trading allowed
DLL imports	MT5 options and EA settings if required	Allowed for current AlgoWayWS-MT5 setup
Webhook UUID	AlgoWayWS-MT5 EA inputs	Correct UUID from AlgoWay dashboard
Connection status	MT5 Experts log	EA connected and receiving messages
Webhook payload	AlgoWay logs	Valid JSON received
Broker permission	Broker account / MT5 server response	Trading and EA trading allowed

Error 4752 vs Webhook Error 415

Do not confuse MT5 Error 4752 with AlgoWay webhook Error 415.

Error	Where it happens	Main cause
4752	MetaTrader 5	EA trading is disabled or prohibited.
415	Webhook/API layer	TradingView sent invalid JSON or wrong content type.

If AlgoWay does not receive the alert correctly, fix the webhook JSON first. If AlgoWay receives the alert and MT5 rejects execution with 4752, fix MT5 algo trading permissions.

Webhook format guide: How to fix AlgoWay webhook Error 415.

Error 4752 vs Error 4756

Error 4752 and Error 4756 are also different.

• 4752 means Expert Advisor trading is disabled or prohibited.
• 4756 means the order request reached the server, but the broker rejected the request parameters.

So if the issue is 4752, first check permissions. If the issue is 4756, check symbol, lot size, filling type, market session, stops, and broker rules.

Common errors hub: MetaTrader 5 common errors in AlgoWay.

TradingView JSON Example for Testing After Fixing 4752

After fixing MT5 permissions, send a safe test message before using your full strategy alert.

{
  "platform_name": "metatrader5",
  "ticker": "EURUSD",
  "order_contracts": 0.01,
  "order_action": "buy"
}

For a TradingView strategy alert, you can use placeholders:

{
  "platform_name": "metatrader5",
  "ticker": "{{ticker}}",
  "order_contracts": "{{strategy.order.contracts}}",
  "order_action": "{{strategy.market_position}}",
  "price": "{{close}}"
}

Confirm the test in both places:

• AlgoWay Webhook Logs — the alert was received and routed.
• MT5 Experts / Journal — the EA attempted execution and no longer returned 4752.

Why AlgoWay Mentions TradingView on a MetaTrader Error Page

Many traders see Error 4752 only after they connect TradingView alerts to MetaTrader 5. That makes it feel like a TradingView problem. In reality, TradingView only starts the automation chain. The actual 4752 rejection happens inside MetaTrader 5 when the EA attempts to trade.

This is why AlgoWay separates the layers:

• TradingView alert layer;
• AlgoWay webhook and JSON layer;
• AlgoWayWS-MT5 connection layer;
• MetaTrader 5 EA permission layer;
• broker execution layer.

Error 4752 belongs to the MetaTrader 5 EA permission layer.

Safe Retest Workflow After Fixing Error 4752

After enabling Algo Trading and EA permissions, do not return immediately to full-size live automation. Retest the chain with the smallest practical order size and a simple payload. The goal is to prove that MetaTrader 5 now allows EA execution before you reconnect the full TradingView strategy.

1. Enable the MT5 toolbar Algo Trading button.
2. Confirm Tools → Options → Expert Advisors permissions.
3. Open EA chart properties and confirm live trading is allowed.
4. Restart or reattach AlgoWayWS-MT5 EA if needed.
5. Send one small fixed test order through AlgoWay.
6. Check AlgoWay Webhook Logs for the received request.
7. Check MT5 Experts and Journal for the new execution result.
8. Confirm that Error 4752 no longer appears.
9. Only then restore the original TradingView alert or strategy automation.

This procedure is useful for both demo and live accounts. It is also useful after a VPS restart, MT5 update, broker server change, account switch, profile change, or reinstall of the AlgoWayWS-MT5 EA. MetaTrader 5 can disable algorithmic trading after certain changes depending on terminal settings, so a route that worked yesterday can suddenly show Error 4752 today.

Cloud MT5, VPS and Error 4752

Many AlgoWay users run MetaTrader 5 on a VPS or cloud desktop so the terminal stays online while TradingView alerts continue to fire. Error 4752 can still appear in that environment. A VPS does not automatically guarantee that algorithmic trading is enabled. After a Windows update, terminal restart, broker reconnect, RDP session change, or migration, the MT5 toolbar and EA permissions should be checked again.

For a VPS-based TradingView to MT5 webhook setup, the minimum healthy state is:

• MT5 terminal is open and logged into the correct trading account;
• AlgoWayWS-MT5 EA is attached to the correct chart;
• Algo Trading is enabled in the toolbar;
• EA properties allow live trading;
• required DLL permissions are enabled when used by the current setup;
• the Experts tab confirms the EA is running and connected;
• AlgoWay logs show incoming webhook alerts;
• the broker account allows trading and is not read-only.

If any of these checks fail, the webhook route may be correct but MT5 execution can still fail. That is why Error 4752 pages should be part of every MT5 automation troubleshooting cluster, together with JSON errors, broker rejection errors, symbol mapping guides and AlgoWayWS-MT5 installation manuals.

SEO Summary for Traders Searching This Error

If you searched for MT5 Error 4752, AutoTrading disabled by client terminal, Trading by Expert Advisors prohibited, Algo Trading disabled MT5, TradingView to MT5 no trade opened, or AlgoWayWS-MT5 EA not placing orders, the core answer is the same: MetaTrader 5 is blocking automated trading. Fix the permission layer first, then test the webhook route again.

AlgoWay can help you identify where the chain fails because webhook logs show whether the signal arrived and MT5 logs show whether the EA was allowed to execute. The clean troubleshooting path is not guesswork. It is layer-by-layer verification from TradingView alert, to AlgoWay webhook, to AlgoWayWS-MT5 EA, to MetaTrader 5 execution permission, to broker server response.

Related AlgoWay Guides

• How to connect TradingView to MetaTrader 5 with AlgoWay EA
• How to install an MT5 Expert Advisor for AlgoWay automation
• MetaTrader 5 common errors in AlgoWay
• How to fix MetaTrader 5 Error 4756
• How to fix AlgoWay webhook Error 415
• AlgoWay JSON schema guide
• Advanced risk management and trade automation

Final Summary

MT5 Error 4752 means MetaTrader 5 is blocking Expert Advisor trading. In most AlgoWayWS-MT5 cases, the fix is to enable Algo Trading globally, allow algorithmic trading in MT5 options, allow the specific EA to trade on the chart, and confirm logs after the next test signal.

If the TradingView alert reaches AlgoWay but MT5 returns 4752, do not rewrite the TradingView strategy first. Fix the MT5 execution permission layer first.