Skip to main content
Get started free
FREE MT5 TOOLS

Every MT5 tool. Free.

Risk, execution and chart tools. No paywalls.

Explore MT5 tools →
7 MT5 tools · all freeWhat is new in the changelog →
COPY TRADES

Four ways to follow.

Copy between your own terminals, free. Hosted options are coming.

See the options →
Not sure which fits? Ask first.Contact us →
Home / Guides / MetaTrader 5 / PFX Executor (part 3 of 3)
Guide · MetaTrader 5 · part 3 of 3 · about 20 minutes

Stop PFX Executor, and run it reliably.Part 3 of 3: the switches, and the 24/7 set-up.

Part 3 shows how to stop the Executor at three levels, how to revoke a terminal key, and how to run it on a virtual server if your PC is not always on. Know the stop switches before you go live. Keep the Executor on a demo until you have tested them.

~20 minstart to finish
7 stepstick each one off
Three stopsfrom gentle to total
Demo firsttest the stops too
✓
Knowing how to stop it matters most.

Stopping is always available: the master switch, the child switch, or revoking the key. If a step doesn't look like the picture, that's normal: open the "Not seeing it?" box under it.

0

Before you start

Parts 1 and 2 must be done, and the test alert must have worked.

Words you'll see. Master switch = the EA's main on/off input. Child switch = the setting under it, marked with a caret (^). Revoke = cancel a key so it stops working.
1

Know the three stop levels

Pick the level that matches what you want to happen.

  1. Stop new entries, keep managing open trades: master switch off, and its caret (^) child off.
  2. Freeze completely: master switch off with the caret child on. This is the default.
  3. Stop everything at the source: revoke the terminal key on the Automation page.
What happens to open trades depends on the level you pick. Check the settings reference for each level before you rely on it.
Not seeing it?

Open trades closed when I turned it off. Check the child switch setting. The three levels above describe what each setting does. Test once on a demo before you rely on it.

2

Revoke a key

Cancel one terminal's key without touching the others.

  1. On the Automation page on precisionfx.io, find the terminal and choose revoke.
  2. The EA on that terminal stops receiving alerts once its key is revoked.
  3. If you lose a key, revoke that terminal and add another. Each key is shown once.
Revoking one key does not affect other terminals or other keys.
Not seeing it?

I revoked a key by mistake. Add the terminal again on the Automation page, copy the new key, and paste it into the EA input.

3

Decide if you need a 24/7 terminal

The EA needs MetaTrader running. A virtual server keeps it running.

  1. If your PC is not on all the time, rent an MQL5 VPS from inside MetaTrader 5.
  2. In the Navigator, right-click your account and choose Register a virtual server.
  3. The product guide says it costs a few dollars a month, paid to MetaQuotes. Check the current price there before you rent.
The Executor runs on a VPS unchanged. It uses no DLL.
Not seeing it?

I can't find Register a virtual server. It sits in the right-click menu on your account in the Navigator. Look for the word virtual.

4

Move it to the VPS safely

Test it on your own terminal first, then move it.

  1. Set up and test the EA on your own terminal first, with Signal source = PrecisionFX Cloud. The Local folder option cannot work on a VPS.
  2. Check https://precisionfx.io is on the WebRequest list, then migrate the VPS: right-click it and choose Synchronize experts, indicators.
  3. Check the VPS journal. It logs the EA's startup banner there. If it says WebRequest is not allowed, add the address again on your own terminal and migrate once more.
Stop the EA on your own PC once the VPS is running it. Two copies with the same key share one queue, and two copies on the same account manage the same trades.
Not seeing it?

Trades are doubled. Two copies are running. Stop the one on your own PC, and check the VPS copy alone.

5

Check the usual causes if nothing happens

Ordered by how often each one is the cause.

  1. Turn on Verbose debug logging. The EA says why it skipped. Read that first.
  2. Check the symbol name exists at your broker with the exact spelling, and the Route key matches exactly.
  3. Check Algo Trading is on, and WebRequest is allowed. A rejected key logs "terminal key rejected". Mint a new one.
The alert log on the Automation page shows every alert, how it was read, and whether each account received it.
Not seeing it?

The log says terminal key rejected. Revoke that terminal on the Automation page, then add it again and paste the new key.

6

Write down your stop plan

Decide before a bad day, not during one.

  1. Write down which of the three stop levels you would use, and who else can use the switch.
  2. Write down your maximum lot size, and why you chose it.
  3. Keep the plan where you can find it, and never with a key or address in it.
Not seeing it?

I don't know which level to pick. Start with the freeze level, which is the default setting, while you look into what happened.

Your safety nets

Three ways to stop it.

1

Master switch

Off, with the caret child on, freezes the EA. Off with the child off also stops new entries.

2

Revoke the key

Cancels one terminal at the source, without touching the others.

3

Maximum lot size

Set it deliberately. It is your last line of defence on every alert.

!

Prop-firm accounts

Automated trading may not be allowed on a challenge or funded account. Read your firm's current rules before you connect the Executor to one.

All done

You're set up.Nicely done.

All guides →All guides →

Risk warning: Trading carries a high risk of loss and is not suitable for everyone. The Executor places real orders from alerts. Stopping it does not close trades that are already open unless you close them yourself. A demo result is not a guide to live results. MetaTrader and MQL5 are trademarks of MetaQuotes Ltd.; PrecisionFX is not affiliated with or endorsed by MetaQuotes.