2026-08-18

Same-login loops and mirror handoff — the boring bugs that break copy automation

Why Same-Login guards and Mirror Ownership leases exist in cloud MT5 copy trading, and how to operate multi-terminal setups without feedback loops.

The unglamorous part of automation

Copy trading looks simple until two terminals argue about who is allowed to trade. Algo stacks fail more often from ownership and identity mistakes than from indicator code.

Same-Login guard

If a Master publisher and a Slave subscriber share one broker login, you can create a feedback loop: the slave mirrors the master, the master republishes the slave, and sizes explode. TradeEcho slaves refuse that configuration (BLOCKED). That is intentional.

Mirror Ownership lease

A second slave on the same path + broker login can steal the lease. The previous instance goes STANDBY and must not keep trading. Prefer one trading instance per login per copy path.

Operator checklist

  • Distinct broker logins for master vs slave
  • Unique account labels per terminal
  • Different magics for MT5 copy vs TV slave when both run

Soft next step

Read the Help entries on BLOCKED and STANDBY, or start a 14-day trial and walk the Setup wizard.

Sources

Back to blog