realtrademasterJoin Discord · 7-day trial ↗

MT5 setup / account and workspace changes

Algo Trading turns off after a switch?

MT5 can disable automated trading after an account, profile or chart change when the matching protective option is selected. Identify the change and the permission that was affected.

An EA may remain attached and continue analysis while trading is prohibited. Check the intended EA and terminal before allowing requests again.

Follow the setup check ↓ · Official sources ↓ · Mechanics checked

Which change came first?

Account changed

Confirm the target account.

The account-change protection disables EA and script trading when the connected account changes. This helps protect a transition such as moving from a demo account to a real one.

Review the account-change option in Tools → Options → Expert Advisors.

Profile changed

Review the loaded workspace.

An MT5 profile stores the chart workspace, including attached EAs. The profile-change protection can prevent trading when another profile is loaded.

Review which charts and EAs came with the profile before deliberately allowing them to trade.

Chart symbol or timeframe changed

Check the attached EA’s permission.

With the chart-change protection selected, changing a chart’s symbol or period can prohibit the EA attached to that chart from trading. Check that EA’s individual permission as well as the platform permission.

The global Algo Trading button alone does not establish that an individual EA is allowed to trade.

Review the selected protections under Tools → Options → Expert Advisors and keep them in place during the checks. A persistent “always on” setup should not be assumed from one permission button.

A careful check after an intentional switch.

  1. Establish the target. Confirm the intended account and the terminal or host you are checking. Use a demo environment for the check.
  2. Review the workspace. Check the loaded charts, EA instances and inputs. A profile may bring a different set of EAs into the workspace.
  3. Identify the affected permission. Read the selected transition protections and that EA’s own trading permission. The platform-wide permission and the EA’s permission both matter for local desktop trading.
  4. Make an intentional decision. After reviewing the target and every loaded EA, decide whether that setup should be allowed to trade again. The transition protections can remain selected.
  5. Observe on demo. Repeat only the relevant transition and note which permission changes. An allowed EA still needs its strategy conditions to be met; permission alone does not confirm an order or fill.

Use the MT5 execution setup worksheet to keep your checks together. For an explicit 10027 or 10026 message, follow the terminal-versus-server permission guide.

Using a VPS? Identify the runtime.

MetaTrader’s built-in virtual hosting has separate permission rules: migrated robots can be allowed to trade while local automated trading is off. Confirm which host you are inspecting. The phone and EA-host guide explains the hosting distinction; MetaQuotes’ migration rules describe the virtual platform.

Bring a clear setup question.

Tell the community which change happened and whether the platform button or one EA was affected. A plain-language description is enough; keep account details and credentials private.

TradeMaster’s Autobot executes analyst signals on a supported, configured MT5 setup. Explore community setup help, dated public bot outcomes including losses, and genuine member reviews. Confirm the supported Windows host, account, licence and risk configuration, and test on demo.

New members get a 7-day signals + Autobot trial. Read the service scope and offer, then bring your setup question.

Explore TradeMaster setup help · 7-day trial ↗

Sources and question context