Two-key activation
The website group and the master EA input must both be enabled.
The copier turns accepted MT4/MT5 order events into account-targeted TradeJournal Pro signals and commands. Followers use the existing leased delivery and acknowledgement path, so retries reuse the same event instead of placing duplicate orders.
The website group and the master EA input must both be enabled.
A repeated broker deal event maps to one master event and one follower delivery.
Follower tickets are linked to the master event before close commands are issued.
EA 8.06 mirrors MT4/MT5 market and pending lifecycles after you explicitly enable the group and master input. Broker symbol suffixes, volume steps, stops, MT4 partial-close ticket behaviour, and MT5 netting rules can still cause a follower rejection. Test every broker pair on demo before live use.
Create a separate token for the MT5 master and each MT4/MT5 follower. Pro and Lifetime include up to three customer broker accounts; the owner override is unlimited.
Replace the old EA file, attach it to one chart per terminal, allow WebRequest to https://tradejournalpro.net, enable AutoTrading/Algo Trading, and confirm every account is Online on the website.
On the master EA, leave ENABLE_MASTER_SOURCE=false while you finish the group. Keep it false on every follower permanently.
Open Account Copier, choose the master, select followers, choose source-lot multiplier or fixed lot, then set a hard maximum lot. Add symbol allow/block lists if required.
Save once with Enable group off. This validates ownership and persists an atomic follower set without allowing a trade yet.
Set ENABLE_MASTER_SOURCE=true on the MT4 or MT5 master only. Optionally set MASTER_SOURCE_MAGIC to capture one strategy magic; zero accepts manual trades. It must differ from TradeJournalEA's own magic. Leave MASTER_SYNC_EXISTING=false unless you deliberately want positions and pending orders already present at startup copied.
Use demo accounts. Test one smallest-size market order, then a pending order through create, entry/SL/TP edit, fill, and cancel. Verify the exact follower ticket changes, partially close the master, then close it fully.
After the dry run is correct, switch Enable group on. Keep the hard cap conservative and monitor the first live-sized sessions manually.