Every setting, explained
Every setting on the app's Settings page and of a listener: what it does, when it applies, and an example. It is the same help the app shows next to each setting.
Trading
Trading enabled
Master switch for this profile. Off, the app stops reading its groups and closes its MetaTrader, so nothing new is placed. What is already at the broker stays there: open trades keep their stop-loss and take-profit, and pending orders can still fill. While it is off the app does not move stops, close One trade shares or look after runners.
How it works, more examples and what to watch out for
This is the on/off switch for the whole profile. While it is on, the app keeps the profile's Telegram connection and its MetaTrader open, reads the groups of its listeners and places what your settings allow.
When you turn it off, the Telegram connection closes within about 30 seconds. A signal that arrives in that gap is recorded as skipped with "Signal skipped — trading is turned off", and a waiting order that expires is cancelled instead of being sent at market.
If the profile uses its own terminal, the app closes that MetaTrader, unless another profile that still trades uses the same one. A terminal you chose yourself stays open.
Your open trades stay at the broker with their stop-loss and take-profit, and pending orders can still fill there. What the app does on its own needs the connection: moving stops after a take-profit, closing the shares of One trade, following runners and closing them before the weekend. None of that runs until you start trading again.
When you turn it back on, MetaTrader starts (with an active licence and a terminal set up) and the listeners reconnect within about 30 seconds. Messages posted while the profile was off can arrive as Telegram catches up; they are judged by when they were posted, so those older than "Max signal age (min)" are skipped.
You go away with two EURUSD trades open, both with the stop at 1.0950 and the take-profit at 1.1100, and turn trading off. Both stay open at the broker and close there at their stop or take-profit. New messages from your groups are not read at all.
A gold signal is open as Split with three trades and "Trailing stop" set to "To the entry". You turn trading off before TP1. TP1 still closes its trade at the broker, but the other two stops stay where they were: the move to break-even needs the app connected.
Your plan allows 1 profile trading at once. "Main" trades and you press "Start trading" on "Demo": it is refused with "Your plan allows 1 profile(s) trading at once. Stop one to start another." Stop "Main" first, then start "Demo".
Off is not "close everything". Nothing is closed for you, and a waiting order at the broker can still fill while you are away, without the app looking after it afterwards.
To stop only one group, turn off that listener's "Enabled" or set its "Mode" to "Watch — record only"; the rest of the profile keeps trading.
The switch syncs with relay2trade.com, where it reads "Pause trading" / "Resume trading". "Restore default settings" and "Set up with a few questions" never change it. If the plan covers fewer profiles than you had trading, it stops the extra ones and the header reads "stopped by your plan".
Dry runs do not start while trading is off, and a profile whose settings do not pass the app's check cannot be started until they are fixed.
Position sizing
One signal is one entry with its stop-loss and take-profits. Risk % of equity and Fixed cash size the whole signal and share it across its take-profits, so 1% on a signal with 4 take-profits is 1% in all, not 4%. With Fixed lots, "Fixed lots are for" decides: every take-profit gets the full lots (0.10 on 4 take-profits is 0.40 in all), or the whole signal shares them. A message with two separate trades is two signals, each sized on its own.
Sizing mode
per listener too
How the lot size of a signal is chosen. All three end at a number of lots; they differ in what stays the same from one signal to the next.
Risk % of equityFixed lotsFixed cash
When it applies
Risk % of equity and Fixed cash need a stop-loss to work the lots out from: the wider the stop, the fewer the lots, and the whole signal shares them across its take-profits. Fixed lots ignore the stop, and "Fixed lots are for" says whether every take-profit gets the full lots or the whole signal shares them.
Example
Same account, same 25-pip stop on EURUSD: Risk 1% of 10 000 → 0.40 lots; Fixed cash 50 → 0.20 lots; Fixed lots 0.10 → 0.10 lots.
How it works, more examples and what to watch out for
Every signal goes through the same steps: first the stop-loss is settled (the signal's, a default one, or your own), then the lots, then the caps, and last the lots are shared across the take-profits.
With "Risk % of equity" the money at risk is your live equity times the percent; with "Fixed cash" it is the amount you type. Both divide that money by what the stop costs on 1 lot: the distance to the stop in points times the value of one point on 1 lot, which MetaTrader works out for the symbol in your account currency.
With "Fixed lots" the stop plays no part in the size. The lots are the number you type, for each take-profit or for the whole signal, as "Fixed lots are for" says.
The result is capped at "Max lots per signal" and at the broker's largest lot, then rounded down to the broker's lot step. If it ends up under the broker's smallest lot, the signal is skipped.
The signal's story shows the working, for example: "Size: 1.00% of 10000.00 USD equity (Risk % of equity) is 100.00 USD at risk for this signal; with the stop 250 points away, that is 0.40 lots in all."
EURUSD buy, 20-pip stop (200 points; one point on 1 lot is worth 1 USD), equity 10 000 USD, 3 take-profits, Split. Risk 1%: 100 / 200 = 0.50 lots, as 0.16 + 0.16 + 0.18. Fixed cash 50: 50 / 200 = 0.25 lots, as 0.08 + 0.08 + 0.09. Fixed lots 0.10 for each take-profit: 3 trades of 0.10, 0.30 in all.
XAUUSD buy at 2400 with the stop at 2395 (5.00 = 500 points; 0.01 on 1 lot is worth 1 USD). Risk 0.5% of 10 000 = 50 USD: 50 / 500 = 0.10 lots. The same signal with the stop at 2390 gives 0.05 lots: the loss at the stop stays 50 USD.
Fixed lots 0.10 on two EURUSD signals, one with a 20-pip stop and one with an 80-pip stop: both trade 0.10, but the first loses 20 USD at its stop and the second 80 USD.
"Risk % of equity" and "Fixed cash" need a stop. When a signal has none, "Require stop-loss" is No and the default stop for its kind is 0, it trades the "Fixed lots" value as the signal's total, even though that field is hidden in these modes (0.01 out of the box).
A market order is sized from the current price, not the entry the signal wrote. If the price has moved toward the stop, the stop is closer and the lots bigger; "Max lots per signal" is the ceiling.
A message with two separate trades (two symbols, or two entries) is two signals, each sized on its own: 1% each is 2% together.
A listener can have its own sizing under "Settings of its own"; its signals then follow that, not the profile's.
Risk % of equity
per signal per listener too
The share of your equity one signal may lose if its stop-loss is hit. The lots are worked out for the whole signal and then shared across its take-profits, so all its trades together risk this much, not each of them. A message with several separate trades (two entries, two instruments) is several signals, and each risks this share. 0.5–1% is a common conservative choice; up to 100% is allowed, the whole account on one stop.
When it applies
Only with the Risk % of equity sizing mode. Equity is read live from MetaTrader when the signal arrives, floating profit and loss included. The lots are rounded down to the broker's lot step and never exceed the lot cap below, so the real risk can come out lower.
Example
Equity 10 000, risk 1%, stop 25 pips on EURUSD (10 per pip per lot): 100 / (25 × 10) = 0.40 lots for the signal. Shared equally across 4 take-profits that is 0.10 lots on each: 1% at risk in all, not 4%.
How it works, more examples and what to watch out for
When a signal arrives, the app reads your equity from MetaTrader at that moment: the balance plus the floating profit or loss of open trades. This percent of it is the money the whole signal may lose at its stop.
That money is divided by what the stop costs on 1 lot, which gives the lots for the signal. With several take-profits the lots are shared by "Share across take-profits" (equally by default), so all the trades together still risk this percent.
The distance is measured from the limit price for a waiting limit order, and from the current price for a market order. A stop closer than the broker allows is pushed out first, which only makes the lots smaller.
The lots are then capped at "Max lots per signal" and at the broker's largest lot, and rounded down to the lot step. Rounding only ever lowers the risk; slippage or a price gap through the stop can still make a real loss larger.
Equity 10 000 USD, 0.5%, EURUSD with a 30-pip stop: 50 / (300 points × 1 USD) = 0.166, rounded down to 0.16 lots. The loss at the stop is 48 USD.
The same account with an open trade 600 USD in loss: equity is 9 400, 0.5% is 47 USD, 47 / 300 = 0.156, so 0.15 lots.
Equity 500 USD, 0.5%, 30-pip EURUSD stop: 2.50 / 300 = 0.008, which rounds down to 0.00. The signal is skipped: "The size came to 0.00 lots, below the broker's smallest lot (0.01)."
Equity 100 000 USD, 1%, 10-pip stop: 1 000 / 100 = 10 lots. With "Max lots per signal" at 5 the signal goes in at 5.00, so the real risk is 500 USD, 0.5%.
It is per signal, not per trade: 1% on a signal with 4 take-profits is 1% in all.
Signals open at the same time add up. Five open signals at 1% each can lose 5% together; "Max signals open at once" and "Max daily loss" put a limit on that.
Up to 100% is accepted, which is the whole account on one stop. Most people stay between 0.25% and 1%.
A signal that ends up with no stop at all is not sized by this: it trades the Fixed lots value.
Fixed lots are for
per listener too
Each take-profit: every take-profit of a signal gets the full lots, so a signal with 4 take-profits puts 4 times the lots in the market. The whole signal: the lots are the signal's total, shared across its take-profits the way a risk-sized signal is.
Each take-profitThe whole signal
When it applies
With "Nearest take-profit only" or "Furthest take-profit only" a signal uses one take-profit, so both choices trade the lots once.
Example
0.05 lots and 4 take-profits: for each take-profit that is 0.20 in all; for the whole signal it is 0.05, as 0.01 + 0.01 + 0.01 + 0.02.
How it works, more examples and what to watch out for
It only matters with "Fixed lots" and a signal that has more than one take-profit.
"Each take-profit": every take-profit gets the full lots. With "Split" that is one trade of that size per take-profit; with "One trade" it is one position of take-profits × lots that closes one share at each take-profit.
"The whole signal": the lots are the signal's total. They are shared by "Share across take-profits" (equally by default), each share rounded down to the lot step, with the rest on the last take-profit. A share under the broker's smallest lot is dropped, furthest take-profit first, and its lots move to the ones kept.
With "Nearest take-profit only" or "Furthest take-profit only" there is one trade, so both choices put the lots in once. A runner ("let the rest run") counts as one more take-profit here: with "Each take-profit" it gets the full lots too.
0.10 lots, 3 take-profits, Split. Each take-profit: 3 trades of 0.10, 0.30 in all. The whole signal: 0.03 + 0.03 + 0.04, 0.10 in all.
0.02 lots for the whole signal, 4 take-profits, smallest lot 0.01: an equal share would be 0.005, too small. The app opens 0.01 at TP1 and 0.01 at TP2; TP3 and TP4 are listed as not placed.
0.10 for each take-profit, 4 take-profits, 20-pip EURUSD stop: 0.40 lots in the market, 80 USD lost if every trade stops out. For the whole signal the same stop costs 20 USD.
"Each take-profit" is the default, so the size grows with the number of targets: a group that posts 5 take-profits puts 5 times your lots in the market.
Margin and the lot limits ("Max margin use %", "Max total lots", "Max lots per symbol") count every trade the signal opens.
On a netting account, or with "One trade", the signal is one position: its total is held under "Max lots per signal" and, when capped, shared evenly.
Fixed lots
per listener too
The lots, whatever the stop distance or the account size: for each take-profit, or for the whole signal, as "Fixed lots are for" says.
When it applies
Only with the Fixed lots sizing mode. The lots are rounded down to the broker's lot step and never exceed the lot cap below or the broker's largest lot.
Example
0.10 for each take-profit on a signal with 3 take-profits: 0.30 lots in the market, as three trades of 0.10 (Split) or one trade of 0.30 that closes 0.10 at each take-profit (One trade). For the whole signal: 0.10 in all.
How it works, more examples and what to watch out for
With "Fixed lots" the number you type is the size, whatever the stop distance and whatever the account's size. "Fixed lots are for" decides whether it applies to each take-profit or to the whole signal.
The lots are rounded down to the broker's lot step and held under "Max lots per signal" and the broker's largest lot. Under the broker's smallest lot the signal is skipped.
This value is also the fallback of the other two modes. With "Risk % of equity" or "Fixed cash", a signal left with no stop at all (none in the signal, "Require stop-loss" No, default stop 0 for its kind) trades these lots as the signal's total, and its story says so.
0.05 lots on EURUSD: a 25-pip stop loses 0.05 × 250 points × 1 USD = 12.50 USD; a 60-pip stop loses 30 USD. Same lots, different risk.
0.05 lots on XAUUSD, buy at 2400 with the stop at 2390: 10.00 on 1 lot is 1 000 USD, so 0.05 lots lose 50 USD at the stop.
You type 0.015 on a broker with a 0.01 lot step: every trade goes in at 0.01.
Only the size is fixed, not the risk. A stop twice as far loses twice as much, and the same 0.10 is a very different position on EURUSD and on gold.
Contract sizes differ between brokers, mostly on indices and coins: one broker's 1 lot of US30 or BTCUSD can be ten times another's. Check the contract before copying a lot size from someone else.
Out of the box it counts for each take-profit, so a signal with 4 take-profits trades 4 times this number.
Fixed cash
per signal per listener too
The money, in the account's currency, one signal may lose if its stop-loss is hit, shared across its take-profits like Risk % of equity: all its trades together risk this amount. You still trade in lots; this only works them out.
When it applies
Only with the Fixed cash sizing mode. The lots are rounded down to the broker's lot step and never exceed the lot cap below, so the real risk can come out lower.
Example
Fixed cash 50, stop 25 pips on EURUSD: 50 / (25 × 10) = 0.20 lots. The same 50 with a 50-pip stop gives 0.10 lots. With 2 take-profits the 0.20 lots are shared as 0.10 on each: 50 at risk in all.
How it works, more examples and what to watch out for
This amount, in your account's currency, is the money the whole signal may lose at its stop. The app divides it by what the stop costs on 1 lot and gets the lots.
Unlike "Risk % of equity", it does not follow your equity: after a win or a loss, the next signal risks the same money.
The value of a price move comes from MetaTrader's own profit calculation for the symbol, so a EUR account trading a USD-priced symbol is converted for you.
The lots are then capped, rounded down to the lot step and shared across the take-profits, so the money really at risk can come out a little under the amount.
50 USD, EURUSD with a 25-pip stop: 50 / 250 = 0.20 lots. With 4 take-profits that is 0.05 on each; 50 USD lost if all stop out.
50 USD, XAUUSD buy at 2400 with the stop at 2395 (500 points, 1 USD per point on 1 lot): 50 / 500 = 0.10 lots.
50 USD on BTCUSD at a broker where 1 lot is 1 BTC, buy at 84 000 with the default crypto stop of 1.5% (1 260 away): 50 / 1 260 = 0.039, so 0.03 lots with a 0.01 step; 37.80 USD at risk.
The amount is in the account's currency: 50 on a EUR account is 50 euros.
A small amount and a wide stop can come out under the broker's smallest lot, and the signal is skipped. Raise the amount or switch to Fixed lots.
As the account grows or shrinks, the amount stays; look at it again from time to time. "Risk % of equity" follows the account on its own.
Max lots per signal
per listener too
The most lots sizing may give. With Risk % of equity, Fixed cash, or Fixed lots for the whole signal, it caps the signal's total before it is shared across the take-profits. With Fixed lots for each take-profit it caps each trade, so a Split signal can put this many lots on every take-profit; a signal held as one trade (One trade, or any signal on a netting account) is capped as a whole and its take-profits share the capped lots. The broker's largest lot applies the same way. The last safety net against a mistyped signal or a tiny stop that would size a huge lot.
When it applies
A capped signal still trades, and its story says so. A listener with its own "Multiple take-profits" follows its own choice.
Example
Sizing gives 1.4 lots and the cap is 1.0: the signal goes in at 1.0, 0.50 on each of 2 take-profits. Fixed lots 0.50 for each take-profit with the same cap: 4 take-profits in Split open 4 trades of 0.50 (2.00 in all); in One trade the position is capped at 1.00 and 0.25 closes at each take-profit.
How it works, more examples and what to watch out for
After sizing, the lots are checked against this cap and then against the broker's largest lot. Over the cap, the signal still trades, at the cap, and its story says "Capped at Max lots per signal (…)".
With "Risk % of equity", "Fixed cash" or Fixed lots for the whole signal, the cap is on the signal's total, before it is shared across the take-profits.
With Fixed lots for each take-profit on a hedging account with "Split" (or a single take-profit), each trade is held to the cap on its own, and the page names it "Max lots per trade". With "One trade", or on a netting account, the signal is one position: take-profits × lots is capped as a whole and shared evenly.
It is 50 out of the box, wide enough not to cut a normal signal. It is there for the mistyped signal or the stop a few points away that would otherwise size a huge lot.
Equity 20 000 USD, Risk 1% = 200 USD, a EURUSD signal whose stop is only 3 pips away (30 points): 200 / 30 = 6.66 lots. With the cap at 2 it goes in at 2.00, and the real risk is 60 USD.
Equity 100 000 USD, 1%, 20-pip stop: 1 000 / 200 = 5 lots. A cap of 1 cuts it to 1.00: 200 USD at risk, 0.2% instead of 1%.
Fixed lots 0.50 for each take-profit, 4 take-profits, cap 1. Split: 4 trades of 0.50, 2.00 in all, each within the cap. One trade: 2.00 is over the cap, so one position of 1.00 with 0.25 closing at each take-profit.
A cap under what your sizing usually gives shrinks every signal without skipping any, so your real risk ends up below your percent. Look for "Capped at" lines in the signal's story.
With Fixed lots for each take-profit on Split, the cap bounds each trade, not the signal: 4 take-profits can put 4 times the cap in the market.
"Max margin use %", "Max total lots" and "Max lots per symbol" are checked after this, on everything the signal opens.
Stop-loss
Require stop-loss
per listener too
Yes: a signal without a stop-loss is skipped; you never enter unprotected. No: it gets the default stop for its kind of instrument below, both as protection and as the distance the lot is sized from — or, where that default is 0, it trades with no stop at your fixed lots.
How it works, more examples and what to watch out for
This decides what happens to a signal that comes without a stop-loss. A stop the signal gives in pips or in percent counts as a stop.
Yes: the signal is skipped and its story says why. Nothing is placed.
No (the default): the app gives it a default stop. It uses "Default stop, any symbol (points) — older setting" when that is above 0, and otherwise the default stop for the symbol's kind: forex, metals, indices and oil, or crypto. The stop is measured from the entry the signal wrote, or from the current price when it wrote none.
That stop protects the trade at the broker and is the distance "Risk % of equity" and "Fixed cash" size from. Where the default for the kind is 0, the trade goes in without a stop, at your fixed lots.
With "Own stop-loss" on, this setting is hidden and not used: every signal gets your stop.
"BUY EURUSD 1.1000 TP 1.1050", no stop. With Yes: skipped. With No and the forex default at 30 pips: the stop goes at 1.0970; on Risk 1% of 10 000 with the price at 1.1000 that is 100 / 300 = 0.33 lots.
"SELL GOLD now TP 2380", price 2400, No, metals default 50 pips: the stop goes at 2405.00 (50 × 0.10 above the price).
No, forex default set to 0, Risk % mode, Fixed lots at 0.01: a EURUSD signal without a stop trades 0.01 lots with no stop, and its story reads "No stop-loss to size by (…), so it trades your fixed lots: 0.01."
Groups that post the stop in a later message are skipped with Yes. With No they go in with the default stop. A later message that moves the stop closer to the price is followed while "Exits and stop moves" is "Follow them", but a stop further away than the default is never moved to.
A trade opened without a stop has no protection at the broker until the group or you set one.
The default stop is measured from the entry the signal wrote. If the price has already passed that point, the stop can land on the wrong side of the price, and the signal is skipped.
A listener can have its own "Require stop-loss" under "Settings of its own"; the four default stops per kind belong to the profile only.
Default stop · forex (pips)
The stop a signal without one gets on forex pairs: 30 pips on EURUSD puts a buy at 1.1000 on a stop at 1.0970. "No stop": such a signal trades without one, at your fixed lots (risk % and fixed cash size by the stop, so they cannot).
When it applies
Only when Require stop-loss is No. The guide suggests a value from what you trade; check it against the signals you follow.
How it works, more examples and what to watch out for
It applies to a signal with no stop, while "Require stop-loss" and "Own stop-loss" are both off and "Default stop, any symbol (points) — older setting" is 0.
The app counts as forex every symbol it does not recognise by name as a metal, an index, oil or gas, or a coin. That includes stocks and symbols with unusual names.
The stop goes this many pips from the entry the signal wrote, or from the current price when it wrote none: below for a buy, above for a sell. A pip is 0.0001 on most pairs and 0.01 on JPY pairs, read from the symbol's digits.
The same stop is what "Risk % of equity" and "Fixed cash" size from, so a wider default stop means fewer lots, not a bigger loss. With "No stop", such signals trade with no stop, at your fixed lots.
30 pips, "SELL EURUSD 1.1000" with no stop: the stop goes at 1.1030.
30 pips, "BUY USDJPY 150.00": a JPY pip is 0.01, so the stop goes at 149.70.
Risk 1% of 10 000 USD on a EURUSD signal without a stop: with 30 pips, 100 / 300 = 0.33 lots; with 50 pips, 100 / 500 = 0.20 lots. Either way about 100 USD is lost at the stop.
A stock or any symbol the app does not recognise counts as forex, and its pip follows its digits: on a stock quoted at 185.20, 30 pips is 0.30.
The stop is set from the stated entry, but a market order is sized from the current price. If the price has moved since the message, the real distance, and the lots, differ from what the numbers suggest.
The four default stops belong to the profile; a listener cannot have its own. A listener whose own "Default stop, any symbol (points) — older setting" is above 0 uses that instead.
Default stop · gold and metals (pips)
The stop a signal without one gets on gold, silver and other metals: 50 pips on gold (a pip is 0.10) puts a buy at 2400 on a stop at 2395. "No stop": such a signal trades without one, at your fixed lots (risk % and fixed cash size by the stop, so they cannot).
When it applies
Only when Require stop-loss is No. The guide suggests a value from what you trade; check it against the signals you follow.
How it works, more examples and what to watch out for
It applies to a signal with no stop on a metal, while "Require stop-loss" and "Own stop-loss" are both off and "Default stop, any symbol (points) — older setting" is 0.
The app knows metals by name, with any broker prefix or suffix: XAU or GOLD, XAG or SILVER, XPT or PLATINUM, XPD or PALLADIUM.
The stop goes this many pips from the stated entry, or from the current price: below for a buy, above for a sell. A gold pip is 0.10 and a silver pip 0.01; platinum and palladium follow their digits, usually 0.01.
The same stop is the distance Risk % and Fixed cash size from. With "No stop", metal signals without a stop trade with none, at your fixed lots.
50 pips, "SELL XAUUSD 2400" with no stop: 50 × 0.10 = 5.00, so the stop goes at 2405.00.
50 pips, "BUY XAGUSD 30.00": 50 × 0.01 = 0.50, so the stop goes at 29.50.
Risk 0.5% of 10 000 USD on a gold buy at 2400 without a stop: the stop at 2395 is 500 points, and at 1 USD per point on 1 lot that is 50 / 500 = 0.10 lots.
Gold can move several dollars in minutes. 50 pips is 5.00, so compare it with the stops your group usually posts on gold before relying on it.
Pips on gold are 0.10, not 0.01: 50 pips is 5.00, not 0.50. Some groups say "points" for 0.10 and some for 1.00; the setting always counts pips of 0.10.
A broker name without any of the metal names above counts as forex, with a pip read from its digits.
Default stop · indices (points), oil (cents)
The stop a signal without one gets on indices, oil and gas: 60 points on US30 puts a buy at 42 000 on a stop at 41 940; on oil the same 60 are cents, 0.60. "No stop": such a signal trades without one, at your fixed lots (risk % and fixed cash size by the stop, so they cannot).
When it applies
Only when Require stop-loss is No. The guide suggests a value from what you trade; check it against the signals you follow.
How it works, more examples and what to watch out for
It applies to a signal with no stop on an index, oil or gas, while "Require stop-loss" and "Own stop-loss" are both off and "Default stop, any symbol (points) — older setting" is 0.
The app knows the common index names (US30, NAS100, US500, GER40, UK100, JP225 and their other spellings) and the energy names (WTI, BRENT, XTI, XBR, OIL, NGAS and similar).
On an index the unit is one whole point of the price. On oil and gas it is the pip read from the digits, usually 0.01, so the number counts cents.
The stop goes this many units from the stated entry, or from the current price, and is the distance Risk % and Fixed cash size from. With "No stop", such signals trade with no stop, at your fixed lots.
60, "SELL NAS100 18 500" with no stop: the stop goes at 18 560.
60, "BUY WTI 75.00": 60 cents, so the stop goes at 74.40.
Risk 1% of 10 000 USD on a US30 buy at 42 000 without a stop, at a broker where one index point on 1 lot is worth 1 USD: the stop at 41 940 is 60 points, so 100 / 60 = 1.66 lots.
One number serves every index, and they move very differently: 60 points is a small move on NAS100 and a larger one on UK100. Pick it for the index you trade most.
Natural gas quoted around 3.00 gets the same 0.60, a fifth of its price. If your groups trade gas, lower this or require a stop.
An index the app does not know by name counts as forex, with a pip read from its digits, and gets the forex default instead.
Default stop · crypto (% of the price)
The stop a signal without one gets on coins: 1.5% puts a BTC buy at 80 000 on a stop at 78 800. "No stop": such a signal trades without one, at your fixed lots (risk % and fixed cash size by the stop, so they cannot).
When it applies
Only when Require stop-loss is No. The guide suggests a value from what you trade; check it against the signals you follow.
How it works, more examples and what to watch out for
It applies to a signal with no stop on a coin, while "Require stop-loss" and "Own stop-loss" are both off and "Default stop, any symbol (points) — older setting" is 0.
The app knows coins by name: BTC, ETH, XRP, SOL, LTC, ADA, DOGE, BNB, DOT, LINK, AVAX, MATIC, TRX, XLM, BCH, SHIB and TON, with any broker prefix or suffix.
Coins are priced too far apart for one pip figure, so this one is a percent of the price: of the stated entry, or of the current price when the signal gives none. The most allowed is 50%.
The stop is also the distance Risk % and Fixed cash size from. With "No stop", coin signals without a stop trade with none, at your fixed lots.
1.5%, "BUY BTCUSD 84 000" with no stop: 1.5% of 84 000 is 1 260, so the stop goes at 82 740.
1.5%, "SELL ETHUSD 3 000": 45 above the price, so the stop goes at 3 045.
1.5%, "BUY XRPUSD 0.5000": 0.0075 below, so the stop goes at 0.4925.
The percent is of the coin's price, not of your account. 1.5% of the price with 1 lot can be far more than 1.5% of the account.
Coins move a lot over a weekend and on news, and a tight percent stops out often. Compare it with the stops your group posts.
A coin the app does not know by name counts as forex and gets the forex default in pips instead.
Default stop, any symbol (points) — older setting
per listener too
The one default stop, in points, every symbol used to get. Above 0 it is still used instead of the defaults per kind of instrument; "Not used" leaves those in charge.
When it applies
Only when Require stop-loss is No. A point is the smallest price step of the symbol; on 5-digit forex 10 points make a pip.
Example
300 points = 30 pips on EURUSD: a buy at 1.1000 gets its stop at 1.0970.
How it works, more examples and what to watch out for
Before the stops per kind of instrument existed, this was the only default stop. It is kept so a setup that relied on it keeps working.
Above 0 it wins over all four stops per kind, on every symbol: a signal without a stop gets its stop this many points from the stated entry, or from the current price. "Not used" hands the choice back to the four stops per kind.
A point is the symbol's smallest price step, so the same number means very different distances: 10 points make a pip on 5-digit forex, and on a 2-digit quote 100 points are 1.00.
300 points on EURUSD (5 digits): 30 pips, a buy at 1.1000 gets its stop at 1.0970.
The same 300 on XAUUSD quoted with 2 digits: 3.00, a buy at 2400 gets its stop at 2397.
The same 300 on US30 quoted with 2 digits: 3 index points, a buy at 42 000 gets its stop at 41 997, a stop most brokers will push out or that closes almost at once.
Leave it on "Not used" unless you trade a single market; the four stops per kind fit each market on their own.
Whole numbers only.
A listener can have its own under "Settings of its own": above 0, it replaces the profile's four stops for that listener's signals.
Own stop-loss
per listener too
Yes: every trade gets your own stop at the distance below, whatever stop the signal gives, and signals without a stop are traded too. The lot is sized from your stop, and breakeven and the ladder move from it. No: the signal's stop is used.
When it applies
Off by default. The signal's own stop is shown next to yours in the signal's story.
How it works, more examples and what to watch out for
With it on, the app ignores the stop the signal gives and places its own, "Own stop-loss (pips)" away from where the order goes in: the current price for a market order, the order's price for a limit or stop order.
Signals without a stop trade too, so "Require stop-loss" and the default stops are hidden and not used.
Everything that depends on the stop follows yours: the lots under "Risk % of equity" and "Fixed cash", the break-even and trailing moves, and the R a runner is measured in. A stop closer than the broker allows is still pushed out to the broker's minimum.
The signal's story shows both, for example "Your own stop-loss: 30 pips → 1.0972 (the signal's stop 1.095 is not used)".
30 pips, "BUY EURUSD 1.1000 SL 1.0950" entered at market with the ask at 1.1002: the stop goes at 1.0972. On Risk 1% of 10 000 that is 100 / 300 = 0.33 lots; with the signal's stop (520 points) it would have been 0.19.
30 pips on a limit listener, sell limit at 1.1050: the stop goes at 1.1080, measured from the order's price.
30 pips, "SELL XAUUSD 2400" with no stop: 30 × 0.10 = 3.00, the stop goes at 2403.00 and the signal trades.
It replaces good stops too. A group that puts its stop behind a level loses that logic, and with Risk % a closer stop means bigger lots.
The distance is in pips of each symbol, so one number fits one market: 30 pips is 0.0030 on EURUSD, 3.00 on gold, 30 points on US30 and 30 USD on BTC. If your groups trade different markets, set it per listener under "Settings of its own".
On a market buy the stop is measured from the ask but triggers on the bid, so the spread eats into it: 5 pips with a 2-pip spread leaves 3.
Own stop-loss (pips)
per listener too
How far from the entry your stop goes, in pips of the symbol traded.
When it applies
A pip is what the market calls one: 0.0001 on most forex, 0.01 on JPY pairs, 0.1 on gold, 1 on indices and crypto. The same number is tight on gold and wide on EURUSD: set it per listener when your groups trade different markets.
Example
30 pips: a EURUSD buy at 1.1000 gets its stop at 1.0970; a gold buy at 2400.0 gets it at 2397.0.
How it works, more examples and what to watch out for
The distance from the order's price to your stop, in pips of the symbol traded.
The app turns pips into price with the pip the market uses: 0.0001 on most pairs, 0.01 on JPY pairs, 0.10 on gold, 0.01 on silver, 1 on the indices it knows and on BTC and ETH. Other symbols follow their digits.
The stop is rounded to the symbol's digits. If it falls closer than the broker allows, it is pushed out to the broker's minimum distance, which sizes the lot down.
It must be above 0 while "Own stop-loss" is on; a save with 0 is refused.
20 pips: a EURUSD sell at 1.1000 gets its stop at 1.1020; a USDJPY buy at 150.00 at 149.80; a gold sell at 2400 at 2402.00.
Risk 0.5% of 10 000 USD with 20 pips on EURUSD: 50 / 200 = 0.25 lots on every signal, whatever stop the signal gives.
100 pips: a US30 buy at 42 000 gets its stop at 41 900; a BTCUSD buy at 84 000 at 83 900, only 0.12% away.
Choose the number for the market you trade most, and give listeners on other markets their own under "Settings of its own".
With Risk % a tight stop means big lots: 5 pips at 1% of 10 000 USD on EURUSD is 100 / 50 = 2.00 lots. "Max lots per signal" caps that.
On market orders the spread counts against the distance, so leave room above the usual spread of what you trade.
Take-profits & trailing
How one signal's size becomes trades: a trade for each take-profit, one trade that closes a share at each, or the whole size on one take-profit.
Multiple take-profits
per signal per listener too
How a signal with several take-profits is traded. Split opens a separate trade for each take-profit, each with its own target at the broker. One trade opens a single trade and closes each take-profit's share of it when the price gets there. Nearest or Furthest take-profit only puts the whole size on that one take-profit. On a netting account Split and One trade both become one position, and the earlier take-profits rest at the broker as orders that close their share.
Split: a separate trade for each take-profitOne trade: a share closes at each take-profitNearest take-profit onlyFurthest take-profit only
When it applies
How much each take-profit gets follows "Share across take-profits", and fixed lots follow "Fixed lots are for". With One trade the shares close only while MetaTrader is open; the stop-loss and the last take-profit stay at the broker. Until the trading bridge in MetaTrader is updated, One trade signals trade as Split.
Example
Take-profits at 2410, 2420 and 2430 with 0.03 lots shared equally: Split opens three trades of 0.01 lots; One trade opens 0.03 lots and closes 0.01 at 2410, 0.01 at 2420 and the last 0.01 at 2430.
How it works, more examples and what to watch out for
The app sorts a signal's take-profits nearest first and turns each one into a part of the signal: TP1, TP2 and so on. A signal that also says to hold (“TP4: hold”, “runner”) gets one more part without a take-profit, the runner.
Split sends one order per part. Each has the signal's stop-loss and its own take-profit, and the broker holds both, so every part closes at its target even when the app or MetaTrader is off.
One trade sends a single order with the whole size, the stop-loss and the last take-profit (no take-profit if the signal has a runner). The earlier take-profits are levels the trading bridge in MetaTrader watches: when the price reaches one, it closes that take-profit's share of the trade.
Nearest and Furthest take-profit only send one order with the whole size on TP1 or on the last take-profit. The other take-profits and any runner part are not used.
Whatever you choose, a signal with a single take-profit is one trade, and a signal with no take-profit is one trade without a target, which the app treats as a runner. On a netting account a symbol can hold only one position, so Split and One trade both become one position whose earlier take-profits rest at the broker as closing orders.
EURUSD buy at 1.1000, stop 1.0970, take-profits 1.1020 / 1.1040 / 1.1060, 0.06 lots for the whole signal, equal shares. Split: three trades of 0.02 lots, with take-profits 1.1020, 1.1040 and 1.1060. One trade: one trade of 0.06 lots with 1.1060 at the broker; 0.02 closes at 1.1020 and 0.02 at 1.1040.
XAUUSD sell at 2400, take-profits 2390 / 2380 / 2370, 0.03 lots. Nearest take-profit only: one trade of 0.03 lots that closes entirely at 2390. Furthest take-profit only: one trade of 0.03 lots that waits for 2370 or the stop.
US30 buy at 42 000, stop 41 850, TP1 42 100, TP2 42 200, “TP3: hold”, 0.03 lots for the whole signal in Split: 0.01 with take-profit 42 100, 0.01 with 42 200, and 0.01 with no take-profit, which your Runners settings look after.
With One trade, the shares before the last take-profit close only while MetaTrader is running. If it is closed when the price passes TP1, that share stays open; the stop-loss and the last take-profit still work at the broker. It also needs the updated trading bridge in MetaTrader: with an older one the signal trades as Split and its story says so.
In Split on a hedging account each part is a position of its own, so it counts toward “Max open positions” and “Max open positions per symbol”. A 4-take-profit signal uses 4 slots.
Nearest take-profit only gives up any move past TP1. Furthest take-profit only keeps the whole size at risk until the last target or the stop, and your trailing stop has nothing to follow.
Max take-profits per signal
per signal per listener too
The most take-profits one signal uses. A leg is one take-profit's part of the signal: its own trade in Split, its share of the one trade in One trade; a runner is a leg too. The nearest take-profits are kept. "No cap": this setting sets no cap of its own.
When it applies
Only with Split or One trade. With Risk % of equity, Fixed cash or Fixed lots for the whole signal, the signal's size is shared across the legs kept; with Fixed lots for each take-profit, fewer legs mean fewer lots. In Split on a hedging account each leg is also a position, so "Max open positions" and "Max open positions per symbol" can trim a signal further.
Example
A signal with 4 take-profits and a cap of 2 uses the two nearest: two trades in Split, or one trade closing a share at each in One trade.
How it works, more examples and what to watch out for
Before sizing the parts, the app counts what the signal wants: one part per take-profit, plus the runner if the signal has one. If that is more than this cap, it keeps the nearest take-profits and drops the rest, the runner first since it comes last.
The size is shared across the parts kept. With Risk % of equity, Fixed cash or Fixed lots for the whole signal your risk stays the same; it is just spread over fewer targets. With Fixed lots for each take-profit, each dropped part is lots you no longer put in.
Every dropped part is listed in the signal's story as “not placed: Max take-profits per signal is” and the number. In Split on a hedging account the position caps can drop more parts after this one, the same way, nearest kept.
With “No cap” this setting sets no cap; the signal's own take-profits and your position caps still bound it.
Cap 3, a signal with 5 take-profits and a runner, 1% risk: TP1, TP2 and TP3 are placed and share the full 1%; TP4, TP5 and the runner are not placed.
Cap 2, Fixed lots for each take-profit at 0.05, a signal with 4 take-profits: two trades of 0.05 lots, 0.10 in total instead of 0.20.
“No cap”, Split, “Max open positions” 10 with 8 already open: a 4-take-profit signal places TP1 and TP2 only, because there are 2 slots left.
A cap of 1 is not the same as Nearest take-profit only in every case: it keeps TP1 and puts the whole size there, but a runner is dropped. If you only ever want one target, choosing that mode is clearer.
The cap alone never makes “Require full signal” skip a signal: a signal cut to the cap counts as complete.
A runner counts as a leg. With a cap equal to the number of take-profits, the runner of a “TP4: hold” signal is the part that goes.
Require full signal
per signal per listener too
Yes: if your limits or the lot sizes cannot fit every take-profit the signal should use (all of them, or as many as "Max take-profits per signal" allows), nothing is placed and the story says why. No: whatever fits is placed, keeping the nearest take-profits.
When it applies
Only with Split or One trade. In Split on a hedging account both the position caps and the broker's smallest lot can leave take-profits out; a signal held as one position (One trade, or a netting account) only loses take-profits to the smallest lot.
Example
Split, 3 take-profits, only 2 position slots left: Yes skips the signal, No places the 2 nearest. With "Max take-profits per signal" at 2 the same signal is complete at 2 and is placed.
How it works, more examples and what to watch out for
The app first works out how many parts the signal should place: every take-profit plus the runner, or fewer if “Max take-profits per signal” is lower. Then it sees how many actually fit.
Two things can make fewer fit: the position caps (“Max open positions”, “Max open positions per symbol”, and a listener's own caps), which apply to Split on a hedging account, and the broker's smallest lot, when a share of the size is too small.
With Yes, if fewer parts fit than it should place, nothing is placed and the story says how many of how many fit. With No, the parts that fit are placed, nearest take-profits first.
0.03 lots on 4 take-profits, equal shares, smallest lot 0.01: only 3 parts of 0.01 fit. Yes: the signal is skipped (3 of 4). No: TP1–TP3 open with 0.01 each.
Split, “Max open positions per symbol” 3, one XAUUSD trade already open, a new gold signal with 3 take-profits: 2 slots left. Yes: skipped. No: TP1 and TP2 are placed.
The same gold signal with One trade: held as one position, it takes one slot, so it is placed in full either way.
With Yes and a small account, sizing that leaves far take-profits under the smallest lot skips signals often. Lower the number of targets with “Max take-profits per signal” instead, or put more on the first take-profits.
It has no effect with Nearest or Furthest take-profit only, where the signal is always one trade.
Trailing stop
per listener too
As each take-profit of a signal is reached, the stop-loss of what is still open moves forward by this rule: the other trades in Split, the rest of the one trade in One trade or on a netting account. A stop only ever tightens, and only when a take-profit is reached, never on a stop-out.
OffTo the entryA fixed step from the entryTo the take-profit beforeJust behind the take-profit reached
When it applies
Needs a signal with at least two take-profits, traded as Split or One trade. “A fixed step from the entry” is anchored on the entry, so uneven take-profits can land it off the real levels; “Just behind the take-profit reached” is the tightest. “To the entry” and “To the take-profit before” can keep some room behind the stop.
Example
A sell at 1000, stop-loss 1100, take-profits 900 / 800 / 700, a pip of 1. To the entry: after TP1 the stop goes to 1000 and stays. To the take-profit before: 1000 after TP1, 900 after TP2. A fixed step from the entry: 900 after TP1, 800 after TP2. Just behind the take-profit reached, 10 pips: 910 after TP1, 810 after TP2. With 50 pips of room behind the stop, to the take-profit before goes to 1050, then 950, then 850.
How it works, more examples and what to watch out for
The app watches the parts of each signal. When one closes at its take-profit, it works out a new stop from this rule and moves the stop-loss of every part still open, runner included.
“Entry” is the price the signal's first trade filled at. To the entry: the stop goes to the entry after TP1 and stays there. To the take-profit before: the entry after TP1, then TP1 after TP2, TP2 after TP3. A fixed step from the entry: after take-profit k the stop goes to entry + k × (TP1 − entry), which after TP1 is TP1 itself. Just behind the take-profit reached: the stop sits “Pips behind the take-profit” from the take-profit just reached, the tightest of them.
With “To the entry” and “To the take-profit before”, “Room behind the stop” puts the stop that many pips further back, toward the loss side, so a dip back to the level does not close what is still open.
A stop is moved only if the new one protects more than the current one. A close at the stop, a manual close or a runner closing never moves anything.
If the broker keeps stops a minimum distance from the price, the stop goes as close as it allows. If the price is already past the new stop, the app closes that part at market, where the stop would have closed it.
The rule used is the one in force when the signal was placed, including a listener's own setting. Changing it later does not change signals already open. After a restart the app picks the open signals back up and keeps moving their stops.
XAUUSD buy at 2400, stop 2390, take-profits 2410 / 2420 / 2430 and a runner. After TP1, TP2 and TP3 the stop of what is left goes to: To the entry 2400, 2400, 2400. To the take-profit before 2400, 2410, 2420. A fixed step from the entry 2410, 2420, 2430. Just behind the take-profit reached with 5 (0.50 on gold) 2409.50, 2419.50, 2429.50. To the take-profit before with 20 pips of room (2.00 on gold) 2398, 2408, 2418.
EURUSD sell at 1.1000, take-profits 1.0980 / 1.0960 / 1.0940, To the take-profit before. TP1 fills: the two trades left get a stop at 1.1000. TP2 fills: the last trade's stop goes to 1.0980, so it can no longer lose.
Uneven targets with Fixed step: buy at 2400, take-profits 2405 / 2430 / 2460. The step is 5, so after TP2 the stop goes to 2410, not to 2405 or 2430.
“A fixed step from the entry” puts the stop on the take-profit that was just reached, where the price is at that moment. A small pullback then closes the rest at once. “To the take-profit before” and “Just behind the take-profit reached” leave room, and “Room behind the stop” adds more to “To the entry” and “To the take-profit before”.
Nothing moves for a signal with one take-profit, or with Nearest or Furthest take-profit only: there is only one part.
With One trade the moves happen only while MetaTrader is running, since that is when the earlier take-profits close.
Runners follow this rule too while the other take-profits are being reached; with runner protection on, whichever stop is tighter is used.
Pips behind the take-profit
per listener too
How many pips behind the take-profit just reached the new stop sits.
When it applies
Only with “Just behind the take-profit reached”.
Example
10 pips, a sell: when TP2 at 800 is reached, the stop of what is still open moves to 810.
How it works, more examples and what to watch out for
Used only by the “Just behind the take-profit reached” rule. When a take-profit is reached, the new stop for what is still open is that take-profit minus this many pips on a buy, plus this many on a sell.
A pip is the symbol's pip: 0.0001 on EURUSD, 0.01 on USDJPY, 0.10 on gold, one point on indices and crypto. The same number therefore means very different distances on different instruments.
The stop only moves if it protects more than the current one, and never closer to the price than the broker allows.
XAUUSD buy, TP1 2410 reached, 5 pips: 5 × 0.10 = 0.50, so the stop goes to 2409.50.
EURUSD sell, TP1 1.0980 reached, 15 pips: 15 × 0.0001 = 0.0015, so the stop goes to 1.0995.
US30 buy, TP1 42 100 reached, 20 pips: one pip is one point, so the stop goes to 42 080.
5 pips is half a dollar on gold and five points on US30: tight enough that normal noise can close the rest right after the take-profit. Pick the number for the instrument the group trades, or give that listener its own value.
A value larger than the distance from TP1 back to the original stop would put the new stop behind the original one; then the stop does not move, because a stop only tightens.
Room behind the stop (pips)
per listener too
How many pips further back than its level the new stop goes: below it on a buy, above it on a sell, so a dip back to the entry or to the take-profit before does not close what is still open.
When it applies
With “To the entry” and “To the take-profit before”.
Example
A sell at 1000, take-profits 900 / 800 / 700, 50 pips of room: after TP1 the stop goes to 1050, after TP2 to 950, after TP3 to 850.
How it works, more examples and what to watch out for
When a take-profit is reached, these rules move the stop to the entry or to the take-profit before; with room, it goes that many pips further back, toward the loss side: below on a buy, above on a sell.
It is for groups that enter over a range: the app fills at the near end, and with no room a dip back to the entry closes what the group still holds.
A pip is the symbol's pip: 0.0001 on EURUSD, 0.01 on USDJPY, 0.10 on gold, one point on indices and crypto.
The stop still only moves forward: if the room would put it behind where it already is, it stays.
XAUUSD buy, the group's zone 2400–2395: the app fills at 2400, the group's average is lower. Take-profits 2410 / 2420, “To the entry”, 30 pips of room (3.00 on gold). TP1 fills: the stop goes to 2397, not 2400, so a dip to 2398 leaves the rest open, as the group's own trade is.
Max jump between take-profits
per signal per listener too
Leaves out a take-profit that is far out of line with the others, because it is probably a typo. The number is how many times bigger than the signal's normal gap between take-profits a gap may be. The take-profits after it are left out too; the rest trade as normal.
When it applies
TP1 and TP2 are always kept. The check starts at TP3.
Example
A short on gold, with the setting at 5:
Entry 4180
TP1 4175
TP2 4168
TP3 4155
TP4 4142
TP5 4120
TP6 4210 – 90 away, when the others are 5 to 22 apart: left out
TP7 4200 – comes after TP6: left out too
The trade runs with TP1 to TP5.
How it works, more examples and what to watch out for
The app measures the gaps from the entry to TP1, TP1 to TP2 and so on, and takes their middle value as the signal's usual step.
From TP3 on, a target more than this many times that step past the one before is left out as a likely typo, with every target after it.
The left-out targets are listed with the signal, each saying why, with a button to this setting.
A signal with no entry price is measured from the price at the time.
Setting 5. Sell at 2400 with targets 2395, 2390, 2385, 2340: the step is 5, 2340 is 45 past 2385 (9 times), so it goes and three targets trade.
Setting 5. Buy at 2400 with targets 2410, 2420, 2450: the step is 10 and 2450 is 30 past (3 times), so all three trade.
A signal with a deliberately far last target (a scalp with one swing target) loses it at a low setting: raise it for such a group, on its listener.
The check reads the signal's own levels, before the price is compared with them.
Runners
Protect runners
per listener too
A runner is a trade with no take-profit: the part of a signal that says to hold (“TP4: hold”, “runner”), or a signal that gives no target at all. With this on, the app follows the runner's stop once it is far enough in profit, so a big move keeps most of what it made instead of riding back to the original stop.
When it applies
The stop only ever moves in the trade's favour. While the signal's other take-profits are still being reached, the stop also follows your trailing stop rule above; whichever stop protects more is used. Changes here also apply to runners already open.
How it works, more examples and what to watch out for
While MetaTrader is connected, the app checks every runner about every 10 seconds. It keeps track of the best price the runner has reached: the bid for a buy, the ask for a sell.
Once the runner is “Start following at” in profit, the app puts its stop “Keep the stop behind by” behind that best price. From then on the stop moves only when the best price improves, and never back.
To avoid a stream of changes at the broker, a stop moves at most once every 15 seconds, only when it improves by at least a tenth of the trail, and never closer to the price than the broker allows.
The weekend close and the time limit are separate settings: they close runners even with protection off. Changes here apply at the next check, also to runners already open.
Defaults (R, start 2, trail 1), XAUUSD buy at 2400, stop 2390: 1R is 10.00. At 2420 following starts and the stop goes to 2410. At 2435 it moves to 2425. The price falls back to 2425 and the runner closes there, 25.00 above the entry.
Protection off, same trade: the price reaches 2435 and falls back to 2390. The runner closes at its original stop, a full 1R loss.
Protection runs in the app, not at the broker. If the app or MetaTrader is closed, the stop stays where it was last put.
A signal with no take-profit at all is a runner too, so these settings also decide how it exits.
While the signal's other take-profits are still being reached, the trailing stop rule also moves the runner's stop; the tighter of the two is used.
Measure in
per listener too
R is how much the trade risks when it opens: the distance from its entry to its original stop-loss. 1R is that distance, 2R twice it. Because it is measured from each trade, 2R means the same thing on gold and on EURUSD — while 100 pips is a small move on gold and a big one on EURUSD.
R — the trade's own riskpips
When it applies
Pips suit one instrument whose moves you know well. A runner opened before this version, whose original stop the app did not keep, can only be followed in pips.
Example
Sell gold at 4316 with the stop at 4324: 1R is 8.00, 2R is 16.00 — the price at 4300.
How it works, more examples and what to watch out for
The unit applies to both “Start following at” and “Keep the stop behind by”.
With R, the app takes the runner's fill price and the stop it opened with; the distance between them is 1R. Each runner has its own R, so the same numbers fit a tight scalp and a wide swing.
With pips, a pip is the symbol's pip: 0.0001 on EURUSD, 0.01 on USDJPY, 0.10 on gold, one point on indices and crypto.
If the unit is R and a runner has no opening stop, or it is on the wrong side, there is nothing to measure from. The app leaves that runner's stop alone and says once that it should be switched to pips.
R, start 2, trail 1. EURUSD buy at 1.1000, stop 1.0970: 1R = 30 pips, so following starts at 1.1060 with the stop at 1.1030. XAUUSD buy at 2400, stop 2390: 1R = 10.00, following starts at 2420 with the stop at 2410.
Pips, start 30, trail 15. EURUSD buy at 1.1000: at 1.1030 the stop goes to 1.1015. On gold the same setting starts after only 3.00 and trails 1.50 behind, which a normal swing can hit.
Pips fit when a listener trades one instrument. If a group posts both gold and forex, R keeps the distances sensible on both, or give each listener its own unit.
A signal without a stop that trades with no stop at all (default stop 0 for that kind of instrument) gives R nothing to measure; use pips for such a listener.
Start following at
per listener too
How far in profit the runner must be before its stop starts to follow, in the unit above. Until then the stop stays where it is.
When it applies
Must be larger than the distance the stop keeps behind the price.
Example
2 (R): the sell at 4316, where 1R is 8.00, starts being followed when the price reaches 4300.
How it works, more examples and what to watch out for
The app measures the runner's profit from its fill price to the best price it has reached. Until that reaches this distance, the runner's stop is not touched by this rule.
When it does, the first move puts the stop at the best price minus the trail on a buy, plus the trail on a sell. Since the trail must be smaller than the start, that first stop is already past the entry.
The app saves settings only when the trail is smaller than this value.
Start 2 R, trail 1 R, US30 buy at 42 000, stop 41 850: 1R is 150 points. Following starts at 42 300 with the stop at 42 150, 150 points of profit locked.
Start 1.5 R, trail 1 R on the same trade: following starts at 42 225 with the stop at 42 075, only 75 points past the entry.
A low start follows the runner early but locks in little at first; a high start lets it breathe but may never begin on a modest move.
The start and the trail share the same unit. Switching from R to pips without changing the numbers turns 2 R into 2 pips.
Keep the stop behind by
per listener too
Once following, the stop sits this far behind the best price the runner has reached, and moves only when that best price improves — never back.
When it applies
Smaller than where following starts, so the very first move already locks in profit. The app changes a stop at most every 15 seconds, and only when the new stop is better by at least a tenth of this distance, so your broker is never flooded with modifications.
Example
1 (R) on that sell: price reaches 4300 → stop 4308; falls to 4290 → stop 4298; bounces to 4296 → stop stays at 4298; rises to 4298 → the runner closes at 4298, keeping 18.00 of the move.
How it works, more examples and what to watch out for
Once following has started, the new stop is the best price reached minus this distance on a buy, plus it on a sell.
The app only sends the change when the new stop is better than the current one by at least a tenth of this distance, at most once every 15 seconds, and not closer to the price than the broker's minimum distance.
A pullback does not move the stop. If the price comes back to it, the broker closes the runner there.
Trail 1 R on a XAUUSD buy at 2400, stop 2390 (1R = 10.00): best price 2440, stop 2430. The price creeps to 2440.80: the stop would improve by 0.80, less than a tenth of 10.00, so it stays at 2430 until the best price reaches 2441.
Trail 15 pips on an EURUSD buy: best price 1.1050, stop 1.1035. The price dips to 1.1045 and the stop stays at 1.1035.
A tight trail keeps more of a move but closes the runner on ordinary noise; a wide one survives pullbacks but gives more back.
After an app restart the best price is not known. If the stop is already in profit, the app assumes the best price was one trail beyond it, so the stop does not jump.
Close runners before the weekend
per listener too
Forex and metals stop trading from Friday 17:00 New York time until Sunday evening. A runner left open over the weekend pays swap and can reopen on Monday far from where it stopped — past its stop, at whatever price the market opens.
When it applies
Timed on New York's clock, so it stays right through daylight saving and whatever time zone your broker's server shows. It closes every runner, including instruments that trade at the weekend.
How it works, more examples and what to watch out for
On Friday, from “Minutes before the weekly close” before 17:00 New York time until 17:00, the app closes every runner at market during its regular check, about every 10 seconds.
Only runners are closed. Trades with a take-profit keep their take-profit and stop over the weekend.
If the broker refuses a close, for example because the symbol is already closed, the app tries again at most once a minute until 17:00.
30 minutes, a gold runner open on Friday: at 16:30 New York time, 23:30 on a broker whose server shows midnight at the close, the app closes it at market.
A BTCUSD runner open on Friday afternoon is closed at the same time, even though crypto trades at the weekend.
The app must be running in that window. If the computer is off on Friday evening, the runner stays open over the weekend.
If you trade crypto at the weekend, turn this off for that listener only, with a setting of its own.
Minutes before the weekly close
per listener too
How long before the Friday close (17:00 New York time) runners are closed.
When it applies
Leave some room: in the last minutes before the close spreads widen, and some brokers stop gold a few minutes early.
Example
30: runners close from 16:30 New York time — 23:30 on the many brokers whose server clock shows midnight at the close.
How it works, more examples and what to watch out for
Sets the start of the Friday window in which runners are closed. The window always ends at 17:00 New York time; with 30 it runs from 16:30 to 17:00.
Accepted values are 1 to 720 minutes, so the window can open as early as 05:00 New York time on Friday.
60: runners close from 16:00 New York time, 21:00 in London, 23:00 on a broker whose server shows midnight at the close.
240: from 13:00 New York time, before the thin Friday afternoon.
Too few minutes risks the close landing in the last minutes when spreads are widest, or after your broker has already stopped gold.
Only used when “Close runners before the weekend” is on.
Close runners after
per listener too
Closes a runner once it has been open this many hours, whatever it is doing.
When it applies
Counted from when the runner was filled. Useful for channels whose “hold” means a day, not a week.
Example
48: a runner filled on Monday at 10:00 is closed on Wednesday at 10:00.
How it works, more examples and what to watch out for
At each check, about every 10 seconds, the app compares how long the runner has been open with this number. Once it is reached, the runner is closed at market, in profit or not.
The time counts from the runner's fill; if that is not known, from the signal. Weekends and closed markets count too: the clock does not pause.
It works whether or not “Protect runners” is on.
24: a runner filled on Tuesday at 14:20 closes on Wednesday at 14:20.
72 with the weekend exit off: a runner filled on Thursday at 09:00 would reach its limit on Sunday at 09:00 while the market is closed, so the close goes through when the market reopens.
The app must be running for the close to happen; if it is off at that moment, the runner closes at the next check after it starts.
Pick the number from how the group trades: a scalping channel's “hold” is hours, a swing channel's can be days.
Safety limits
The label next to each limit says what it counts: one signal, each trade, everything open, one symbol, the day or the profile's MetaTrader account.
Max open positions
all open at once per listener too
The most positions the app may have open at once, from every listener. Pending orders count too, and each trade of a Split signal is a position of its own; a signal held as one trade (One trade, or any signal on a netting account) is one position.
Example
Cap 20 with 18 open: a Split signal with 3 take-profits is trimmed to 2, or skipped when "Require full signal" is Yes.
How it works, more examples and what to watch out for
Before a signal is placed, the app counts what it already has open on this profile: every open position plus every pending order it placed. Trades you opened by hand are not counted.
If that count has reached the cap, the signal is skipped. If there is at least one free slot, the signal goes ahead and is then fitted to the free slots.
A Split signal needs one slot per take-profit. With fewer slots than take-profits, the nearest take-profits are placed and the rest are listed as not placed. With "Require full signal" on, the whole signal is skipped instead.
A signal held as one trade ("One trade" mode, or any signal on a netting account) needs one slot, whatever its number of take-profits.
A pending order holds its slot until it fills, expires or is cancelled.
Cap 10, 7 open. A Split signal on EURUSD with 4 take-profits: 3 slots free, so the 3 nearest take-profits are placed and the fourth is listed as not placed.
Cap 10, 7 open, "Require full signal" on. The same 4-take-profit signal is skipped: it would need 4 slots and only 3 are free.
Cap 10, 9 open trades and 1 pending limit on XAUUSD 2400. A new signal is skipped: the pending order counts as the tenth.
Your plan caps this setting; the Desk shows your plan's limit under Account → "Plan & billing". You cannot save a higher value, and if your plan goes down the app lowers it to the plan's limit. Trying to save more shows how to raise the limit.
It must be at least 1; there is no "off". It counts per profile, across every listener of that profile.
With many take-profits per signal the cap fills fast: 10 slots hold only 3 signals of 3 take-profits. Choose "One trade" under "Multiple take-profits" or lower "Max take-profits per signal" if you want more signals open at once.
Max open positions per symbol
per symbol per listener too
The most positions on the same symbol at once, counted the same way.
When it applies
Hedging accounts only. A netting account holds one position per symbol by nature, so it takes no new signal on a symbol until that position is closed.
How it works, more examples and what to watch out for
The same count as "Max open positions", made for one symbol: the app's open positions and pending orders on the signal's symbol, buys and sells together.
A signal is skipped when that symbol is already at the cap. Otherwise a Split signal is trimmed to the free slots on that symbol, nearest take-profits first, or skipped as a whole with "Require full signal" on.
Both caps apply: a signal gets the smaller of the free slots on the profile and on the symbol.
Max open positions per symbol 4, two XAUUSD signals of 2 trades each open. A third gold signal is skipped; a EURUSD signal still goes in.
Max open positions per symbol 3, one XAUUSD buy open. A gold sell with 3 take-profits places its 2 nearest: buys and sells share the same count.
Shown only on hedging accounts. On a netting account the app takes no new signal on a symbol while it has a position there, whatever this says.
It must be at least 1. Set it well under "Max open positions" if you want no single instrument to take all your slots, for example when several groups trade gold.
Max signals open at once
all open at once per listener too
How many signals may have trades or pending orders open at once; a new signal is skipped while this many are live.
When it applies
Counts signals, not trades: a Split signal with 3 trades is one signal.
How it works, more examples and what to watch out for
The app groups its open trades and pending orders by the signal that placed them and counts the signals. A Split signal with 3 trades still open is one; once its last trade closes, it no longer counts.
When a new signal arrives and that count has reached the cap, the signal is not placed. On an Auto listener it waits on the Dashboard for your approval instead of being skipped, because this is often a signal you still want.
"Place anyway" on that waiting signal lifts this one limit for it. Every other rule still applies.
An app trade whose signal the app cannot trace counts as a signal of its own.
Cap 3. Open: a EURUSD signal with 3 trades, a XAUUSD signal with 2, a US30 signal with 1. That is 3 signals, so a fourth waits for you on the Dashboard.
Cap 3, same situation, then the US30 trade hits its stop. Two signals remain, so the next signal is placed by itself.
It counts signals, not trades. To limit trades use "Max open positions".
A pending limit that has not filled yet keeps its signal counted. Long waiting-order expiries can hold the cap full with nothing actually open.
A signal held for approval expires if you do not act on it within 10 minutes.
Max total lots
all open at once per listener too
Cap on the lots the app has open across all symbols, pending orders included. A signal whose trades together would push it over is skipped.
When it applies
Bounds size, where the position caps above only bound count.
Example
2.5 lots open, cap 3.0: a signal of 0.40 lots in all goes in, one of 0.60 is skipped. Fixed lots of 0.20 for each of 3 take-profits make a signal of 0.60.
How it works, more examples and what to watch out for
After the signal is sized, the app adds up the lots of all its trades and adds them to the lots it already has open on this profile, pending orders included.
If the sum is above the cap, the whole signal is skipped. It is not shrunk to fit.
Only trades the app placed count; lots you opened by hand are left out.
A signal refused by this cap can be placed anyway from the app, which sets your lot and margin limits aside for that one signal.
Cap 2.00, 1.50 lots open. Risk sizing gives a XAUUSD signal 0.20 per take-profit on 3 take-profits = 0.60. 1.50 + 0.60 = 2.10, so it is skipped.
Same cap and open lots, but the next signal comes out at 0.45 in all: 1.50 + 0.45 = 1.95, so it is placed.
Lots are not the same risk on every instrument: 1 lot of EURUSD and 1 lot of BTCUSD are very different amounts. This cap adds them as plain numbers.
With risk sizing, a tighter stop gives more lots for the same risk, so a signal with a close stop is the one most likely to hit this cap.
Max lots per symbol
per symbol per listener too
Cap on the lots the app has open on one symbol, pending orders included. A signal whose trades together would push that symbol over is skipped.
How it works, more examples and what to watch out for
The same test as "Max total lots", on the signal's symbol only: lots already open or pending on that symbol plus the lots of all the new signal's trades.
If that is above the cap, the whole signal is skipped; it is not trimmed. Other symbols are not affected.
Both lot caps apply, and "Place anyway" sets both aside for one signal.
Cap 1.00 per symbol, 0.80 lots open on XAUUSD. A gold signal of 0.30 is skipped (1.10), a EURUSD signal of 0.30 goes in.
Cap 0.50 on a small account trading gold and BTCUSD: it keeps any one instrument from growing past half a lot, however many groups send it.
One number for every symbol. A cap that suits EURUSD may be tight for gold or loose for BTCUSD.
It counts by the broker's symbol, so XAUUSD and XAUUSD.s are the same symbol only if your account uses one name.
Max traded signals per day
per day per listener too
The most signals traded in a day, from every listener. A signal counts once it has placed a trade or a pending order, however many trades it opens.
When it applies
The day starts again at midnight on the broker's server clock, and the count survives an app restart.
Example
Cap 5: five signals with 3 take-profits each can open 15 trades; a sixth signal that day is skipped.
How it works, more examples and what to watch out for
The app keeps a count of the signals it traded today on this profile, from every listener. A signal adds 1 once it has placed at least one trade or pending order, whatever the number of trades.
When the count reaches the cap, every new signal that day is skipped. Follow-ups on trades already open still work.
The day is the broker's server day: the count restarts at midnight on the server clock. It is rebuilt from the app's own records at start, so a restart does not reset it.
A pending order that later expires unfilled still counted, because it was placed.
Cap 3. Signals at 09:10 (placed), 10:30 (skipped by the spread guard), 12:00 (placed), 15:45 (placed). A 17:20 signal is skipped: the skipped one did not count, the other three did.
Broker server at UTC+3, you in UTC+1. The count restarts at 23:00 your time, not at your midnight.
This is your own limit and is separate from your plan's daily signal quota. The quota counts signals the server read, resets at 00:00 UTC, and is set by your plan (the Desk shows it under Account → "Plan & billing"); this setting counts signals the app placed, by the broker's day.
A listener can have its own "Max traded signals per day", counting only its signals and never above this one.
Max daily loss
per day per listener too
Circuit breaker: once today's result is this far in the red, no new trades open until the next day. It counts the trades closed today (losses minus wins), and with "Count open trades" what the app's open trades float at too. The switches under it say what else happens at the limit: delete the pending orders, close the trades in loss, close the trades in profit. The next setting says whether this figure is money or a percent of the account's value at the start of the day.
When it applies
Net, so a win earlier in the day buys back room. It counts every trade the app closed today, from every listener, and survives an app restart.
Example
Breaker 200: after −150, −100 and +80 (net −170) trading continues; one more −40 (net −210) stops it for the day.
How it works, more examples and what to watch out for
The app adds up the result of every trade it closed today on this profile: losses, wins, partial closes and netting exits, from every listener.
Before each new signal it compares that net result with the line. Once the loss reaches the line, no new trade opens for the rest of the broker day.
Open trades are not touched, and their floating result does not count until they close.
The line is money or a percent of the account's value at the start of the day, as "Daily loss limit is in" says. It resets at the broker's midnight and survives a restart.
That is with the switches under it off. "Count open trades" reads the line with what the app's open trades float at; "At the limit: delete pending orders", "close trades in loss" and "close trades in profit" act on what is open the moment the day reaches it. All three leave the account flat until the broker's midnight.
Line 300 USD. Closed today: −120, −90, +60, −110 = −260. Trading goes on. The next close is −50 (net −310): no new trades until the broker's midnight.
Line 300 USD, closed −200, and an open gold trade floating at −250. New signals still trade: only closed results count. If that trade closes at −250, the day is at −450 and trading stops.
It is a stop for new trades, not a stop-loss. With the switches under it off, losses can run past the line through trades already open. To have the app close its losing trades when the day reaches the line, turn on "At the limit: close trades in loss", and "Count open trades" to read the line with them.
"Force placement" is not offered for a signal it stopped: it holds until the next day.
Only trades the app placed count.
A listener can have its own "Max daily loss", counted on its own trades and never above this one. As a percent it can be at most 100. Its switches are the profile's unless it sets its own, and they act on its own trades and orders only.
Daily loss limit is in
Type the daily loss limit as money (200) or as a percent of what the account was worth when the day started (2). A percent limit is worked out again each day, so it follows the account up and down.
account moneypercent of the account's value at the start of the day
When it applies
That value is taken at the broker's server midnight, the moment the day's counters restart, and it includes what was floating then. Until a terminal has connected on a new day there is no opening balance, so a percent limit does not stop anything.
Example
2% on an account that opened the day at 10,000 stops trading at −200 for that day; if tomorrow opens at 12,000 the line is −240.
How it works, more examples and what to watch out for
With "account money", the number under "Max daily loss" is the line itself, in the account's currency.
With "percent of the account's value at the start of the day", the app takes the account's equity at the broker's midnight, floating results included, and works the line out from it. It keeps that figure, on your computer and on the website, so a restart later that day, or the app brought back on another computer, keeps the same line.
If the app is not running at midnight, the figure is taken the first time it reads the account that broker day.
The unit also applies to every listener's own "Max daily loss".
Percent, 3. Monday opens at 10 000: line −300. Tuesday opens at 9 500: line −285.
Percent, 2, and at midnight a trade floats at −400 on a 10 000 balance. The day's value is 9 600, so the line is −192.
Switching the unit does not convert the number: 200 as money becomes 200% as a percent, which the app refuses (a percent is at most 100). Retype the value after switching.
Until a terminal has connected on a new day, a percent line has no starting value and stops nothing.
Count open trades
per listener too
Read the limit on today's closed result plus what the app's open trades are floating at, each time MetaTrader reports them. Off: only the trades closed today count, and what is still open does not.
How it works, more examples and what to watch out for
Off (the default): before each new signal the app compares the result of the trades it closed today with the limit. Open trades do not count until they close.
On: the app also adds what its open trades are floating at, each time MetaTrader reports them, about every 2 seconds. The moment the sum reaches the limit, no new trade opens for the rest of the broker day, and the limit holds from the result it was reached at, even if the open trades come back.
What else happens at that moment is up to the three switches under it.
Limit 300 USD, closed today −180, a gold trade floating at −130. On: the day stands at −310, past the limit, and no new trades open. Off: the day stands at −180 and new signals still trade.
Limit 300 USD, on, the day touches −300 with a trade floating at −150, then the trade comes back to −20. The limit holds from −300: no new trades until the broker's midnight.
Floating results move with every price, so a day can touch the limit on one spike. It needs MetaTrader 5 running and connected to the app to see the open trades.
A listener's own "Max daily loss" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
At the limit: delete pending orders
per listener too
When the day reaches the limit, the app deletes its pending entry orders (limit and stop orders still waiting to open), so none of them opens a trade later that day. The take-profits a netting position keeps are left.
How it works, more examples and what to watch out for
New trades stop at the limit whatever these switches say, until the broker's next day. Each of the three adds one thing, on its own: delete the pending orders, close the trades in loss, close the trades in profit.
All three on leave the account flat and quiet until the broker's midnight: nothing open, nothing waiting.
The limit is read as "Count open trades" says: on the closed result alone, or with what the open trades float at.
Each closed trade's signal story and a notice on the bell say what was done and why.
Limit 300 USD, "Count open trades", "delete pending orders" and "close trades in loss" on: closed −180, open XAUUSD −145, EURUSD −15, USDJPY +40. The day reaches −300: the app closes XAUUSD and EURUSD, deletes its GBPUSD pending order and leaves USDJPY running. If USDJPY later turns into a loss, it is closed then.
All three on and "Count open trades" on: at −300 the app closes every trade it has open and deletes its pending orders. The day ends near −300 and the account stays flat until the broker's midnight.
Trades close at market price, so the day can end a little past the line. It needs MetaTrader 5 running and connected to the app; if the broker refuses a close, for example while the market is shut, the app tries again every 30 seconds. Trades and orders you opened yourself in MetaTrader, or another expert opened, are never counted or touched.
A listener's own "Max daily loss" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
At the limit: close trades in loss
per listener too
When the day reaches the limit, the app closes each of its open trades that is in loss, at market. While the day stays at or past it, a trade that turns into a loss later is closed then.
How it works, more examples and what to watch out for
New trades stop at the limit whatever these switches say, until the broker's next day. Each of the three adds one thing, on its own: delete the pending orders, close the trades in loss, close the trades in profit.
All three on leave the account flat and quiet until the broker's midnight: nothing open, nothing waiting.
The limit is read as "Count open trades" says: on the closed result alone, or with what the open trades float at.
Each closed trade's signal story and a notice on the bell say what was done and why.
Limit 300 USD, "Count open trades", "delete pending orders" and "close trades in loss" on: closed −180, open XAUUSD −145, EURUSD −15, USDJPY +40. The day reaches −300: the app closes XAUUSD and EURUSD, deletes its GBPUSD pending order and leaves USDJPY running. If USDJPY later turns into a loss, it is closed then.
All three on and "Count open trades" on: at −300 the app closes every trade it has open and deletes its pending orders. The day ends near −300 and the account stays flat until the broker's midnight.
Trades close at market price, so the day can end a little past the line. It needs MetaTrader 5 running and connected to the app; if the broker refuses a close, for example while the market is shut, the app tries again every 30 seconds. Trades and orders you opened yourself in MetaTrader, or another expert opened, are never counted or touched.
A listener's own "Max daily loss" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
At the limit: close trades in profit
per listener too
When the day reaches the limit, the app closes each of its open trades that is in profit (or at nought), at market, keeping what they made. While the day stays at or past it, a trade that turns into a profit later is closed then.
How it works, more examples and what to watch out for
New trades stop at the limit whatever these switches say, until the broker's next day. Each of the three adds one thing, on its own: delete the pending orders, close the trades in loss, close the trades in profit.
All three on leave the account flat and quiet until the broker's midnight: nothing open, nothing waiting.
The limit is read as "Count open trades" says: on the closed result alone, or with what the open trades float at.
Each closed trade's signal story and a notice on the bell say what was done and why.
Limit 300 USD, "Count open trades", "delete pending orders" and "close trades in loss" on: closed −180, open XAUUSD −145, EURUSD −15, USDJPY +40. The day reaches −300: the app closes XAUUSD and EURUSD, deletes its GBPUSD pending order and leaves USDJPY running. If USDJPY later turns into a loss, it is closed then.
All three on and "Count open trades" on: at −300 the app closes every trade it has open and deletes its pending orders. The day ends near −300 and the account stays flat until the broker's midnight.
Trades close at market price, so the day can end a little past the line. It needs MetaTrader 5 running and connected to the app; if the broker refuses a close, for example while the market is shut, the app tries again every 30 seconds. Trades and orders you opened yourself in MetaTrader, or another expert opened, are never counted or touched.
A listener's own "Max daily loss" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
Daily profit target
per day per listener too
Once today's result is this far in profit, no new trades open until the next day. It counts the trades closed today (wins minus losses), and with "Count open trades" what the app's open trades float at too. The switches under it say what else happens at the target: delete the pending orders, close the trades in loss, close the trades in profit. The next setting says whether this figure is money or a percent of the account's value at the start of the day.
When it applies
Net, so a loss later in the day takes the target back out of reach. It counts every trade the app closed today, from every listener, and survives an app restart.
Example
Target 300: after +150, +120 and −40 (net +230) trading continues; one more +90 (net +320) stops it for the day.
How it works, more examples and what to watch out for
The app adds up the result of every trade it closed today on this profile: wins, losses, partial closes and netting exits, from every listener.
Before each new signal it compares that net result with the target. Once the profit reaches it, no new trade opens for the rest of the broker day.
Open trades are not touched, and their floating result does not count until they close.
The target is money or a percent of the account's value at the start of the day, as "Daily profit target is in" says. It resets at the broker's midnight and survives a restart.
That is with the switches under it off. "Count open trades" reads the target with what the app's open trades float at; "At the target: delete pending orders", "close trades in loss" and "close trades in profit" act on what is open the moment the day reaches it. All three bank the day: the account stays flat until the broker's midnight.
Target 400 USD. Closed today: +180, −60, +150 = +270. Trading goes on. The next close is +160 (net +430): no new trades until the broker's midnight.
Target 400 USD, closed +350, and an open gold trade floating at +200. New signals still trade: only closed results count. If that trade closes at +200, the day is at +550 and trading stops.
With the switches under it off it stops new trades only: trades already open keep running and can give part of the day's profit back. To bank the day at the target instead, turn on "Count open trades" and the three "At the target" switches.
"Force placement" is not offered for a signal it stopped: like the daily loss, it holds until the next day.
A listener can have its own "Daily profit target", counted on its own trades and never above this one. As a percent it can be at most 100. Its switches are the profile's unless it sets its own, and they act on its own trades and orders only.
Daily profit target is in
Type the daily profit target as money (300) or as a percent of what the account was worth when the day started (3). A percent target is worked out again each day, so it follows the account up and down.
account moneypercent of the account's value at the start of the day
When it applies
That value is taken at the broker's server midnight, the moment the day's counters restart, and it includes what was floating then. Until a terminal has connected on a new day there is no opening balance, so a percent target does not stop anything.
Example
3% on an account that opened the day at 10,000 stops trading at +300 for that day; if tomorrow opens at 12,000 the target is +360.
How it works, more examples and what to watch out for
With "account money", the number under "Daily profit target" is the target itself, in the account's currency.
With "percent of the account's value at the start of the day", the app takes the account's equity at the broker's midnight, floating results included, and works the target out from it. It keeps that figure, on your computer and on the website, so a restart later that day, or the app brought back on another computer, keeps the same target.
If the app is not running at midnight, the figure is taken the first time it reads the account that broker day.
The unit also applies to every listener's own "Daily profit target".
Percent, 2. Monday opens at 10 000: target +200. Tuesday opens at 10 400: target +208.
Percent, 2, and at midnight a trade floats at +500 on a 10 000 balance. The day's value is 10 500, so the target is +210.
Switching the unit does not convert the number: 300 as money becomes 300% as a percent, which the app refuses (a percent is at most 100). Retype the value after switching.
Until a terminal has connected on a new day, a percent target has no starting value and stops nothing.
Count open trades
per listener too
Read the target on today's closed result plus what the app's open trades are floating at, each time MetaTrader reports them. Off: only the trades closed today count, and what is still open does not.
How it works, more examples and what to watch out for
Off (the default): before each new signal the app compares the result of the trades it closed today with the target. Open trades do not count until they close.
On: the app also adds what its open trades are floating at, each time MetaTrader reports them, about every 2 seconds. The moment the sum reaches the target, no new trade opens for the rest of the broker day, and the target holds from the result it was reached at, even if the open trades come back.
What else happens at that moment is up to the three switches under it.
Target 400 USD, closed today +350, a gold trade floating at +60. On: the day stands at +410, past the target, and no new trades open. Off: the day stands at +350 and new signals still trade.
Target 400 USD, on, the day touches +400 with a trade floating at +120, then the trade falls back to +20. The target holds from +400: no new trades until the broker's midnight.
Floating results move with every price, so a day can touch the target on one spike. It needs MetaTrader 5 running and connected to the app to see the open trades.
A listener's own "Daily profit target" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
At the target: delete pending orders
per listener too
When the day reaches the target, the app deletes its pending entry orders (limit and stop orders still waiting to open), so none of them opens a trade later that day. The take-profits a netting position keeps are left.
How it works, more examples and what to watch out for
New trades stop at the target whatever these switches say, until the broker's next day. Each of the three adds one thing, on its own: delete the pending orders, close the trades in loss, close the trades in profit.
All three on leave the account flat and quiet until the broker's midnight: nothing open, nothing waiting.
The target is read as "Count open trades" says: on the closed result alone, or with what the open trades float at.
Each closed trade's signal story and a notice on the bell say what was done and why.
Target 400 USD, all four switches on: closed +250, open XAUUSD +180 and EURUSD −30. The day reaches +400: the app closes both trades and deletes its GBPUSD pending order, so the day is banked near +400.
Target 400 USD, "Count open trades" and "close trades in profit" on only: at +400 the app closes XAUUSD (+180) and keeps EURUSD (−30) running, and its pending orders stay. If EURUSD turns into a profit later that day, it is closed then.
Trades close at market price, so the day can end a little past the line. It needs MetaTrader 5 running and connected to the app; if the broker refuses a close, for example while the market is shut, the app tries again every 30 seconds. Trades and orders you opened yourself in MetaTrader, or another expert opened, are never counted or touched.
A listener's own "Daily profit target" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
At the target: close trades in loss
per listener too
When the day reaches the target, the app closes each of its open trades that is in loss, at market. While the day stays at or past it, a trade that turns into a loss later is closed then.
How it works, more examples and what to watch out for
New trades stop at the target whatever these switches say, until the broker's next day. Each of the three adds one thing, on its own: delete the pending orders, close the trades in loss, close the trades in profit.
All three on leave the account flat and quiet until the broker's midnight: nothing open, nothing waiting.
The target is read as "Count open trades" says: on the closed result alone, or with what the open trades float at.
Each closed trade's signal story and a notice on the bell say what was done and why.
Target 400 USD, all four switches on: closed +250, open XAUUSD +180 and EURUSD −30. The day reaches +400: the app closes both trades and deletes its GBPUSD pending order, so the day is banked near +400.
Target 400 USD, "Count open trades" and "close trades in profit" on only: at +400 the app closes XAUUSD (+180) and keeps EURUSD (−30) running, and its pending orders stay. If EURUSD turns into a profit later that day, it is closed then.
Trades close at market price, so the day can end a little past the line. It needs MetaTrader 5 running and connected to the app; if the broker refuses a close, for example while the market is shut, the app tries again every 30 seconds. Trades and orders you opened yourself in MetaTrader, or another expert opened, are never counted or touched.
A listener's own "Daily profit target" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
At the target: close trades in profit
per listener too
When the day reaches the target, the app closes each of its open trades that is in profit (or at nought), at market, keeping what they made. While the day stays at or past it, a trade that turns into a profit later is closed then.
How it works, more examples and what to watch out for
New trades stop at the target whatever these switches say, until the broker's next day. Each of the three adds one thing, on its own: delete the pending orders, close the trades in loss, close the trades in profit.
All three on leave the account flat and quiet until the broker's midnight: nothing open, nothing waiting.
The target is read as "Count open trades" says: on the closed result alone, or with what the open trades float at.
Each closed trade's signal story and a notice on the bell say what was done and why.
Target 400 USD, all four switches on: closed +250, open XAUUSD +180 and EURUSD −30. The day reaches +400: the app closes both trades and deletes its GBPUSD pending order, so the day is banked near +400.
Target 400 USD, "Count open trades" and "close trades in profit" on only: at +400 the app closes XAUUSD (+180) and keeps EURUSD (−30) running, and its pending orders stay. If EURUSD turns into a profit later that day, it is closed then.
Trades close at market price, so the day can end a little past the line. It needs MetaTrader 5 running and connected to the app; if the broker refuses a close, for example while the market is shut, the app tries again every 30 seconds. Trades and orders you opened yourself in MetaTrader, or another expert opened, are never counted or touched.
A listener's own "Daily profit target" acts the same way on that listener's trades and orders only. It takes these switches from the profile unless it sets its own under "Settings of its own".
Max margin use %
MetaTrader account
Skip a signal whose trades, all together, would push the account's margin in use above this share of equity.
When it applies
Checked after sizing: (margin already in use on the account + margin the signal's trades need) / equity × 100. It cannot be turned off; 100 lets margin in use reach your whole equity.
Example
Equity 10 000, margin in use 2 000, the signal needs 1 500: 35%. Fine under a 50% cap, skipped under 30%.
How it works, more examples and what to watch out for
After sizing, the app asks MetaTrader how much margin one lot of the symbol needs, multiplies it by the lots of all the signal's trades, and adds the margin already in use on the account.
That total divided by the account's equity, times 100, must not be above this percent. If it is, the whole signal is skipped.
This reads the whole account: margin held by trades you opened by hand counts too, and so do floating losses, because they lower equity.
When the broker gives no margin figure for the symbol, or equity is unknown, the check is not made.
Leverage 1:100, EURUSD at 1.1000: one lot needs about 1 100 USD. Equity 10 000, margin in use 2 000, a signal of 3 × 0.50 lots needs 1 650. (2 000 + 1 650) / 10 000 = 36.5%: placed with a 50% cap, skipped with 30%.
Equity 1 000, nothing open, a symbol whose smallest lot needs 1 200 of margin: 120%. No setting helps here; the message says the account is too small for that symbol.
It cannot be turned off. Allowed values are above 0 and up to 100; 100 lets margin in use reach your whole equity, where brokers start closing positions (stop out).
"Place anyway" sets this cap aside for one signal, but never past 100%: trades that need more margin than the account has are not sent.
Margin per lot depends on your leverage and on the instrument, so the same lots can pass on EURUSD and fail on an index.
Lowest equity to trade
MetaTrader account
Kill-switch: no new trades while account equity is below this amount. Open positions are left alone.
When it applies
Equity is read live from MetaTrader, so floating losses count.
How it works, more examples and what to watch out for
Before each new signal, the app reads the account's equity live from MetaTrader: balance plus the floating result of everything open, including trades you opened by hand.
If equity is below the floor, the signal is skipped. Nothing is closed.
There is nothing to reset: as soon as equity is back above the floor, the next signal trades again.
While equity is unknown (MetaTrader not answering), this check is not made.
Floor 9 000 on a 10 000 account. Balance 9 400 and open trades at −500: equity 8 900, new signals are skipped. The trades recover to −200: equity 9 200, signals trade again.
Floor 4 500 on a 5 000 account used for one group: after 500 of losses in total, closed or floating, the app opens nothing more until you lower the floor or add funds.
It is a fixed amount, not a percent. After a deposit or withdrawal, check it still sits where you want.
It does not close open trades.
It is the same for every listener; a listener cannot change it.
Pause between signals (seconds)
per listener too
Minimum seconds between entries: a signal arriving within this window of the last placed one is skipped.
When it applies
Across all listeners; a signal's trades go in together and count as one entry.
How it works, more examples and what to watch out for
The app remembers when it last placed a signal on this profile, from any listener. A new signal arriving sooner than this many seconds after it is skipped.
A skipped signal does not restart the clock; only a placed one does. All the trades of one signal go in together and count as one entry.
The skipped signal is not queued for later. After a restart the time of the last entry is read back from the app's records.
Cooldown 60. Placed at 10:00:00. A signal at 10:00:42 is skipped (42 seconds). One at 10:01:05 is placed, and the next 60 seconds count from 10:01:05.
Two groups post the same gold call 20 seconds apart. With a 120-second cooldown only the first is placed, even if the levels differ too much to count as a duplicate.
It blocks every signal in the window, not only repeats. A group that sends two different pairs in one burst loses the second. For repeats, the duplicate check is the finer tool.
A listener can have its own cooldown, counted from its own last entry; it may be longer than the profile's.
Max spread (points)
per signal per listener too
Skip a market entry when the current spread (ask minus bid) is wider than this many points; a guard against thin, news-driven conditions.
When it applies
Market entries only, a limit that turns into a market order included; a resting limit does not cross the spread.
Example
EURUSD quoted 1.10000 / 1.10012 is a 12-point spread: skipped with a cap of 10.
How it works, more examples and what to watch out for
Right before a market entry, the app reads the current bid and ask and turns the difference into points, the smallest price step of that symbol.
If the spread is wider than the cap, the whole signal is skipped.
It is checked for market entries and for a pending limit that expires and is sent to market. A limit left waiting in the book is not checked, because it fills at its own price.
A listener can set its own value, including "Off" to turn the guard off for that group only.
EURUSD 1.10000 / 1.10018: 18 points (1.8 pips). Skipped with a cap of 15, placed with 20.
XAUUSD 2400.10 / 2400.45: 35 points on a 2-decimal quote. A cap of 20 set for forex would block most gold signals.
BTCUSD 84 000.00 / 84 018.00: 1 800 points. Give a crypto group its own value, or "Off".
Points are not pips: on 5-digit forex 10 points = 1 pip, on 2-digit gold 100 points = 1.00. The same number means very different things across instruments.
Spreads widen at the daily rollover and around news; a tight cap skips signals at those times, which is often the point.
Max slippage (points)
per trade per listener too
Sent to the broker with every market order: a fill further from the quoted price than this is rejected by the broker itself.
Example
20 points on EURUSD is 2 pips of tolerance.
How it works, more examples and what to watch out for
Every market order the app sends carries this number as the largest distance, in points, the fill may be from the price the app asked for.
The broker applies it. On accounts with instant or request execution, a fill further away is refused. On market-execution accounts many brokers fill at the price available and ignore it.
When a limit is sent to market because the price is already better or the order expired, the allowed slippage can be tightened further, so the fill never lands worse than the stated entry.
A listener can set its own value.
20 points on EURUSD: asked 1.10000 for a buy, a fill up to 1.10020 is accepted.
20 points on XAUUSD is 0.20, which gold often moves in a second. If gold entries are refused with "price changed" or a requote, raise it to 100–300 for that group.
Too low and orders are refused in fast markets, so trades you wanted are missed. Too high and entries can fill far from the signal.
It is in points like the spread guard, so one value rarely suits forex, gold, indices and crypto alike; use a listener's own value where needed.
The group's messages after a signal
What a group posts about a trade that is already open: close it, cancel it, move its stop or target, close part of it. The app reads these like signals and acts only on this group's own trades.
Exits and stop moves
per listener too
Instructions that protect a trade already open: close it (“close”, “exit”, “stop the trade”), cancel an order that has not filled yet (“cancel the pending”), move the stop-loss to the entry (“SL to BE”) or closer to the price, or have it follow the price (“trail your SL 100 pips behind the price”). Followed, the app carries them out on this group's trades; ignored, it notes them and leaves the trade to your settings. A stop is only ever moved closer, never further away; a move to a price the market is already past would close the trade at once, so the stop stays and the app says why. A move given only in pips (“SL 20 pips”) is left to your trailing stop and runner settings.
Follow themIgnore them
When it applies
Ignored unless you turn them on. Follow them for a group you trust to look after its trades: a group that says “close now” usually sees something coming, and ignoring it can cost the whole stop-loss. Leave them ignored if you want only your own settings to decide.
Example
You hold a gold buy from the group and it posts “Close gold now”. Followed: the app closes that trade and cancels its orders still waiting. Ignored: the trade stays open with its stop-loss and take-profit.
How it works, more examples and what to watch out for
When the group posts a message that is not a new signal, the app reads it for instructions. It then finds which of this listener's own trades the message is about: the signal it replies to; otherwise the one open trade on the symbol it names; otherwise the only trade open from that listener. If more than one could fit, it changes nothing and says why.
This setting covers closing the trade, cancelling its orders that have not filled, moving the stop to the entry and moving it to a tighter price. “Close” closes the signal's open positions and also cancels its orders still waiting.
The stop only ever moves closer. Break-even uses the entry the signal stated, or each position's own open price for a market signal. If the broker keeps stops a minimum distance from the price, the stop goes as close as it allows.
With Ignore them, each instruction is still recorded in Activity and the signal's story, marked as not followed, and nothing changes. Follow-ups never count toward your daily signals.
You hold an XAUUSD buy at 2400 with stop 2390, the price is 2412, and the group replies to its signal “SL to BE”. Followed: the stop moves to 2400.
Same trade, the price is 2395 and the group posts “move SL to entry”. A stop at 2400 would close the trade at once, so the stop stays at 2390 and the app says why.
A buy limit on EURUSD at 1.0980 has not filled and the group posts “cancel”. Followed: the waiting order is deleted. The group then posts “SL 1.0950” for a trade whose stop is 1.0970: refused, because it would widen the stop.
Listeners in Watch only record the instruction; Manual listeners apply it without asking.
With two open trades on the same symbol from one group, a message that names the symbol but does not reply to a signal changes nothing. Groups that reply to their own signal message give the surest results.
A move given only in pips (“SL 20 pips”) is never followed; that is what your trailing stop and runner settings do. A message older than “Max signal age (min)” when the app reads it is not applied.
Partial closes and target moves
per listener too
Instructions that manage the profit of a trade already open: close part of it (“close 20%”, “take half”) or move its take-profit. Your own settings already decide this: how a signal is shared across its take-profits, how the stop moves at each one, and runners. Followed, the group's instruction is carried out as well; ignored, it is noted and your settings keep managing the trade.
Follow themIgnore them
When it applies
Leave them ignored unless you trust how a group manages its trades more than your own settings. Both at once can surprise you: a partial close from the group on top of the share your settings already close at TP1.
Example
The group posts “TP1 hit, close 20% and move SL to breakeven”. With these ignored and exits followed, the app moves the stop to the entry and closes nothing more: what closes at TP1 is what your settings put there.
How it works, more examples and what to watch out for
This covers two instructions: closing part of a trade (“close 20%”, “take half”) and moving its take-profit to a new price. The app finds the trade the same way as for exits.
A partial close takes that share of the signal's open lots, rounded down to the broker's lot step. Whole trades go first, the one with the nearest take-profit first and the runner last; what is still to close comes out of the next trade. It never closes more than asked, and a trade closed in part keeps at least the broker's smallest lot.
A take-profit move changes the target and keeps the stop.
With Ignore them, each such instruction is recorded as not followed, and your own take-profit, share and trailing settings keep managing the trade.
Split, three trades of 0.02 lots on gold (TP1, TP2, TP3), followed. The group posts “close half”: half of 0.06 is 0.03, so the TP1 trade closes whole (0.02) and 0.01 comes out of the TP2 trade.
One trade of 0.01 lots and “close 50%”: half is 0.005, under the smallest lot 0.01, so nothing is closed and the app says so.
EURUSD buy with take-profit 1.1040 and the group posts “move TP to 1.1060”. Followed: the target moves to 1.1060. Ignored: it stays at 1.1040.
Followed together with several take-profits, a group's “close 20% at TP1” comes on top of what your settings already close at TP1, so you can end up with far less open than either intended.
Closing part of one position needs the updated trading bridge in MetaTrader; with an older one, only whole trades are closed and the app says what stayed open.
A target given only in pips is never followed.
Repeated, late and opposite signals
Duplicate window (min)
How far back to look for a duplicate. A signal whose resulting trade matches one placed recently, from any listener (same symbol and side, every level within the tolerance below), waits for your review on the Dashboard instead of trading.
Example
Two "buy XAUUSD 2400 sl 2390 tp 2410" messages 3 minutes apart with a 5-minute window: the second one waits for you.
How it works, more examples and what to watch out for
For each signal it places, the app remembers the broker symbol, the side and the stated entry, stop-loss and take-profits, for this many minutes. This covers every listener of the profile.
A new signal is a duplicate when, within that window, a placed one has the same symbol and side, both have an entry or neither does, both have a stop or neither does, the same number of take-profits, and every level within "Duplicate tolerance (pips)".
On an Auto listener a duplicate is not traded. It waits on the Dashboard marked "duplicate" or "possible duplicate", and expires after 10 minutes if you do nothing. On Manual and Watch listeners it is only marked.
Signals that were skipped or only watched are not remembered, so they never make a later one a duplicate. A restart keeps the window.
Window 5, tolerance 10. 14:00 buy XAUUSD 2400 sl 2390 tp 2410 2420 is placed. 14:03 the group reposts it with entry 2400.50: 5 pips off, so it waits as "possible duplicate".
Same first signal. 14:04 buy XAUUSD 2400 sl 2390 tp 2410, one take-profit only: a different shape, so it trades normally.
Same first signal. 14:07 the exact same message: the 5-minute window has passed, so it trades as a new signal.
Groups that re-enter the same setup on purpose ("add another position") will see those waiting. Approve them, or shorten the window.
A sell is never a duplicate of a buy. A duplicate that is not traded is given back to your plan's daily signal quota.
It is the profile's setting; a listener cannot change it.
Duplicate tolerance (pips)
How close two signals' levels must be to count as the same trade: every level within this many pips.
When it applies
Only with a duplicate window above 0.
How it works, more examples and what to watch out for
When the duplicate check compares a new signal with one placed recently, each level is compared on its own: entry with entry, stop with stop, first take-profit with first take-profit, and so on.
The difference is measured in pips of that symbol. Every level must be within this number for the signal to count as a duplicate. If all differences are 0 it is marked "duplicate"; otherwise "possible duplicate".
A pip follows the instrument: 0.0001 on EURUSD, 0.01 on USDJPY, 0.10 on gold.
Tolerance 10 on EURUSD. First: buy 1.1000 sl 1.0970 tp 1.1040. Second: buy 1.1006 sl 1.0970 tp 1.1040. The entry is 6 pips off, the rest equal: possible duplicate.
Tolerance 10 on XAUUSD (a pip is 0.10, so 10 pips = 1.00). Stops at 2390 and 2388.50 are 15 pips apart: not a duplicate.
"Exact match only" still checks duplicates, but only exact matches. To turn the check off, set "Duplicate window (min)" to "Off".
A wide tolerance can hold back a real second signal at a nearby level. On gold, 10 pips is only 1.00.
Max signal age (min)
A message that reaches the app more than this many minutes after it was posted is never traded. From 1 to 60 minutes; there is no "no limit".
When it applies
Only delayed and replayed messages; a live message is seconds old. One posted while the app was off, asleep or offline is picked up only if it is still within this limit, and then it waits for your approval instead of trading by itself. Older ones are left out entirely. One that Telegram delivers late while the app is connected is listed as stale, with the delay.
Example
A 20-minute outage with the limit at 5: the signals posted in the last 5 minutes of it wait for your approval, the earlier ones are not picked up.
How it works, more examples and what to watch out for
Every Telegram message carries the time it was posted. When a message reaches the app, the app compares that time with now.
A live message is a few seconds old and always passes. A message older than this limit is never read as a signal or traded.
When the app was off, asleep or offline and catches up, messages posted within the limit are picked up but wait for your approval instead of trading by themselves; older ones are left out without a record.
When Telegram delivers a message late while the app is connected, a message over the limit is listed as stale, with its delay.
Limit 5. The computer wakes at 09:12 after sleeping since 08:40. Signals posted at 09:08 and 09:10 wait for your approval; the one from 08:55 is not picked up.
Limit 2 on a scalping group: a message Telegram delivers 3 minutes late while connected is listed as stale and not traded.
From 1 to 60 minutes; there is no "no limit". A higher limit catches more after an outage, but the price may have moved far from the signal. "Max entry deviation" on the listener is the guard for that.
It is the profile's setting; a listener cannot change it. A message edited later keeps its original time.
Opposite-direction signals
per signal per listener too
What a signal does when its listener already has trades or waiting orders on the symbol the other way: open it beside them, ask you first (it waits in Approvals), skip it, close them and then trade it, or only close them (read as an exit).
Open it beside themAsk meSkip itClose them, then trade itClose them only
When it applies
Only that listener's own trades and orders on that symbol count; another group's trades are not its own. Closing is at market, and waiting orders are cancelled.
Example
Holding three buys on gold from a group that now posts a sell: with "Ask me" the sell waits for you; with "Close them, then trade it" the buys close and the sell goes in.
How it works, more examples and what to watch out for
Before a signal trades, the app looks for its listener's trades and waiting orders on the same symbol in the other direction.
If there are some, it does what this setting says. "Ask me" puts the signal in Approvals with a note; approving it trades it beside them.
The two closing choices close them only if the signal itself would trade, so a misread or refused signal never closes anything.
On a netting account, which holds one position per symbol, "Open it beside them" is refused as before and an approval closes the open position first.
"Skip it". A group holding a sell on EURUSD posts a buy: the buy is skipped with the reason, the sell stays.
"Close them, then trade it". Two buys and a waiting buy limit on gold, then a sell: the limit is cancelled, the buys close at market, and the sell is placed as its message says.
"Close them only" treats the group's change of direction as an exit, even when the new signal has levels.
With the listener in watch or approval mode, the signal still goes through those first.
Trading days and hours
Trading days
per listener too
Days when the app may open trades, on your broker's server clock: mon, tue, wed, thu, fri, sat, sun.
How it works, more examples and what to watch out for
Before each signal the app takes today's weekday from the broker's server clock, not your computer's, and checks it against this list.
On a day not in the list the signal is skipped. It is not held for the next allowed day.
Only new entries are affected. Trades and pending orders already open keep running, and a pending limit that expires on a day off is not sent to market.
A listener can have its own trading days.
mon, tue, wed, thu, fri on a UTC+3 server. A signal at 23:30 Friday your time (UTC+1) is 01:30 Saturday on the server: skipped.
A crypto group on its own listener keeps all seven days, while the profile trades mon–fri: its BTCUSD signals trade at weekends, forex groups do not.
Write days as three lowercase letters in English: mon, tue, wed, thu, fri, sat, sun. At least one day is required.
Forex opens on Sunday evening on most servers; leave sun in if you want those first hours.
Trading hours
per listener too
Only open trades inside this window, on your broker's server clock, e.g. 08:00-22:00. Empty = always. An overnight window such as 22:00-06:00 works too.
When it applies
Signals outside the window are skipped, not queued.
How it works, more examples and what to watch out for
The window is written as HH:MM-HH:MM and read on the broker's server clock, the time MetaTrader's Market Watch shows.
A signal is placed only when the server time falls inside it. Both end minutes count as inside, so 08:00-22:00 still trades at 22:00 and not at 22:01.
If the start is later than the end, the window runs over midnight: 22:00-06:00 trades from 22:00 to 06:00.
Signals outside are skipped, not queued. Open trades are not closed. The trading days are checked first, by the day on the same clock.
You want 09:00–18:00 Bucharest time (UTC+3 in summer) and the server runs UTC+3: type 09:00-18:00. With a UTC+2 server, type 08:00-17:00.
22:00-06:00 with trading days mon–fri: a signal at 02:00 server time Saturday is skipped, because Saturday is not a trading day, even though 02:00 is inside the hours.
Server time is often 2–3 hours ahead of UTC and changes with daylight saving on the broker's side. Check Market Watch rather than your clock.
Empty means any hour. A window with the same start and end, such as 08:00-08:00, trades only in that one minute, not all day.
A listener can have its own hours; empty as its own means around the clock for that group.
Symbols
Group vocabulary is normalized during parsing (GOLD → XAUUSD) and your broker's endings (XAUUSD.s) are matched automatically, so most people configure nothing here. Name a symbol yourself only when your broker calls it something else. The whitelist is an optional safety net.
Symbol names at your broker
For an instrument your broker calls something else. On the left the word signals use (GER40, US100, GOLD), on the right the symbol exactly as MetaTrader shows it (DE40, USTEC, XAUUSD.pro). The app then trades that symbol whenever a signal names the word.
When it applies
Add a row only when a signal is skipped with "your broker has no symbol…". Endings such as .s, .pro or m are found by the app itself and need no row. A row covers every spelling of the word: US100, NAS100 and NASDAQ are one instrument.
Example
Signals say GER40, your broker lists DE40: row GER40 → DE40. The mark next to the symbol says whether your broker has it.
How it works, more examples and what to watch out for
When a signal names an instrument, the app first looks the word up in this list. A row found there wins; the app then trades exactly the symbol on its right.
Without a row, the app uses its built-in names (GOLD → XAUUSD, US100 and NASDAQ → NAS100 and so on) and then finds your broker's version of the symbol, endings such as .s, .pro or m included.
A row covers every spelling of its word: the left side is read the same way as the channel's word, so US100, NAS100 and NASDAQ are one row.
The symbol on the right is kept exactly as you typed it, upper and lower case, because some brokers tell XAUUSDm from XAUUSDM.
A group posts "US30 buy 42 000" and your broker lists the Dow as DJ30. The signal is skipped with "your broker has no symbol called US30". Add US30 → DJ30 and the next one trades on DJ30.
Your broker has both XAUUSD and XAUUSD.pro, and you want the .pro one with lower spreads: add GOLD → XAUUSD.pro. Every gold signal, written GOLD or XAUUSD, goes to XAUUSD.pro.
Most accounts need no row. Add one only after a signal was skipped for a missing symbol, or to choose between two versions your broker offers. The skipped signal has a button that adds the row for you.
No spaces, commas, semicolons or = in either side. A row that names itself (US30 → US30) does nothing and is removed.
A wrong symbol on the right sends every such signal to the wrong instrument. Check the mark next to it, which says whether your broker has it.
Allowed symbols
If set, only these symbols may ever be traded, from any listener. Empty = no restriction. Write each one as the Signals page shows it (XAUUSD for gold) or as your broker spells it (XAUUSD.s), separated by commas.
How it works, more examples and what to watch out for
With the list empty, any symbol may be traded. With anything in it, a signal whose symbol is not on the list is skipped, from every listener of the profile.
Each entry is read the way a signal's symbol is: the plain name (XAUUSD), a word the app knows (GOLD), a spelling with a space or slash (EUR/USD), or your broker's own name (XAUUSD.s) all match a gold or euro signal.
This check happens before the listener's own "Symbols" list. A symbol must pass both.
Whitelist XAUUSD, EURUSD, GBPUSD. A group sends a US30 signal: skipped, with a message naming the list. A GOLD signal passes, since GOLD means XAUUSD.
Whitelist EURUSD, XAUUSD and one listener's "Symbols" XAUUSD. That listener trades only gold; the other listeners trade gold and EURUSD.
Once you add one symbol, everything else is blocked. When a new instrument is skipped, check this list first.
A listener cannot loosen it; its own "Symbols" only narrows it further. Separate entries with commas; spaces and semicolons work too.
Listener settings
These belong to each listener, so every signal group can have its own rules. Under "Settings of its own", a group can also set any setting marked "per listener too" differently from your profile; whatever it does not set follows the profile.
Name
How this listener shows up across the app. Change it freely; history stays attached.
How it works, more examples and what to watch out for
The name is how this listener appears everywhere in the app: in the list on the Listeners page, in Listener performance on the Dashboard, on each signal it brought, and on the website and in the office.
When you pick a group with Choose…, the name fills in from the group's title. You can change it at any time.
Renaming changes nothing else. Past signals, open trades, waiting orders and the listener's own limits stay attached to the listener, not to its name, so a rename keeps its whole history.
In a group with topics, each signal shows the listener and the topic together, for example “Gold VIP › Signals”.
You pick the group “FX Signals Premium 🔥”. The name fills in as that title. You rename it to “FX Premium”: last week's 14 signals and the 2 open trades now show under “FX Premium”.
Two listeners read the same group with topics: name them “Gold – Auto” and “Forex – Manual”, so the Dashboard and the approval list tell you at a glance which rules a signal went through.
A refused save because of a limit names the listener by this name (“Listener Gold VIP: its own Max daily loss …”), so a clear name makes such messages easy to follow.
Two listeners can share a name; nothing stops it, but the Dashboard and the signal list then cannot tell them apart for you.
Group / channel
The group or channel to read. Click Choose… to pick from your Telegram groups, or type @handle for a public channel.
How it works, more examples and what to watch out for
This is the Telegram group or channel the listener reads. The app reads it through your own Telegram account, connected on the Connections page, so you must be a member of the chat.
Choose… lists the groups and channels your connected account is in, with a search box. Pick one and the name fills in from its title. You can also type a public channel's @handle, or an id: -100… for a channel or supergroup, - followed by digits for a small group.
Only new messages are read: a message edited after it was posted is not read again. Captions of photos count as text. Your own messages in the chat are read too.
Several listeners may point at the same chat. A message goes to only one of them: the first in the list that reads its topic. On a chat without topics, that is always the first.
You click Choose…, search “gold” and pick “Gold Signals VIP”. The listener starts reading it at once; no restart is needed.
A public channel you have not joined: type @forexsignalsdaily. The app opens it by its handle; if Telegram will not open it, the listener says why.
You leave the group in Telegram. The listener's dot on the Dashboard turns amber and the listener says the chat is not in your account's chat list: no message from it reaches the app until you join again.
A chat you only archived in Telegram still works, even though the listener may say it is not in your chat list.
The group or channel can only be changed in the desktop app; the website editor shows it but cannot change it.
Telegram must be connected and the profile's trading switched on for any listener to read. With trading off, the Telegram connection is closed and messages posted in that time are not traded.
Topics
This group has topics: one chat split into several threads, such as signals, results and discussion. "All topics" reads every message in the group; click Choose… to read only the topics you tick.
When it applies
Tick only the topic where signals are posted. In a discussion topic any member's message is read like the provider's, and "close all" written there can close your trade.
Example
Two listeners on the same group can split it: one on "Gold signals" in Auto, one on "Forex signals" in Manual. A message goes to the first listener that reads its topic.
How it works, more examples and what to watch out for
Some Telegram groups have topics: one chat split into threads, such as Signals, Results and Discussion. For the app it is still one chat, and every message carries the topic it was posted in. This setting appears only for such a group.
“All topics” reads every message in the group, whatever the thread. Choose… opens the group's topic list; tick the ones this listener reads and click “Use these”.
A message goes to one listener only: the first in the list that reads its topic. So two listeners on the same group can split it by topic, each with its own mode and rules.
Every signal says which topic it came from, in the app, on the website and in the office. A dry run on this listener replays only messages from the topics you ticked.
A group has three topics: “Gold signals”, “Forex signals” and “Chat”. Listener A reads only “Gold signals” in Auto; listener B reads only “Forex signals” in Manual. “BUY XAUUSD 2400 SL 2390” in “Gold signals” trades on A; “SELL EURUSD 1.1000” in “Forex signals” waits for your approval on B; nothing in “Chat” is read.
A listener on “All topics” has a gold buy open. A member writes “close all” in the discussion topic. That message is read like the provider's and can close your trade. Tick only the signals topic to prevent it.
In a discussion topic any member's message is read like the provider's. Chatter can parse as a signal, and instructions such as “move SL to BE” can act on your open trade.
The order of listeners matters when two read the same topic: the first one in the list takes the message and the second never sees it.
Topics are chosen in the app, or in the Desk with “Choose topics” on the listener; either way the app asks Telegram for the list, so it has to be running. The office shows them read-only. A listener set up before topics were supported keeps reading all of them until you choose.
What does this group usually trade?
When a message from this group names no instrument (“I'm buying - 4134”), it is traded on this one. Pick it from your broker's list. A message that names its instrument is always traded on the one it names. Empty: a signal with no instrument is not traded. The lists of allowed symbols still decide.
Read calls without a number
Some groups post a call as a few words with no price at all: “GOLD BUY NOW”. The app normally sets every message without a number aside unread, because in most groups such a line is talk. On, a short message that names an instrument and a side (buy, sell, long, short) is read as a signal and traded at the market by this listener's and the profile's rules. Off, it is set aside and its record says why.
When it applies
Only for a group that really trades on such lines. Each one read counts as a reading of your plan's day, and a call with no stop-loss is refused while “Require stop-loss” is on.
Example
“GOLD BUY NOW” or “SELL EURUSD”: read with this on. “Gold looks strong today” names no side and “buy now guys” names no instrument: neither is ever read.
Enabled
No pauses this listener: its messages are ignored until you turn it back on.
How it works, more examples and what to watch out for
On, the listener reads its group and handles each message by its mode. Off, the listener is paused: the app stops reading the chat for it, and nothing posted there in that time is recorded or traded.
Pausing keeps everything else: the listener's settings, its history, and any trades or waiting orders it already placed. Those stay open and keep being managed (take-profits, trailing, runners, expiry of waiting orders).
Your plan sets how many listeners may run at once, counted across all your profiles; a switched-off listener does not count. The Desk shows your plan's limit under Account → "Plan & billing"; level 10 and level 40 add one more each, and cards can add more for a while.
Your plan and your level allow 4 listeners at once. You have 4 on and add a fifth: it is created switched off, with the note that your plan allows 4 at once. Switch one of the others off to switch it on.
You pause “Gold VIP” while it has a buy open at 2400 with a stop at 2390. The trade stays open and closes at its stop or take-profit as usual; a “close now” posted in the group while paused is not read.
You move to a plan that runs one listener at once while two are on. At the next licence check the app switches off the newest one and tells you: “Listener … switched off: your plan allows 1 running at once.” Nothing is deleted.
A paused listener does not read follow-up instructions either. A “close” or “move SL to BE” from the provider while it is off is missed, and your open trade keeps its own stop and take-profit.
A waiting limit that expires while its listener is off does not go to market: the listener being switched off stops it, whatever “If the limit order expires” says.
To stop trading without losing the instructions, set Mode to Watch instead: it keeps reading and recording, and places nothing.
Mode
What happens to a signal from this group.
Auto — trade immediatelyManual — wait for my approvalWatch — record only
When it applies
Start a new group in Watch to see how its signals would have done, move to Manual to confirm each one on the Dashboard, and to Auto only once you trust it.
How it works, more examples and what to watch out for
Mode decides what happens to a signal from this group once it is read.
Watch — record only: the signal is recorded and never placed. The record also says what your rules would have done at that moment: the orders it would have placed, with lots, stop-loss and take-profit, or the reason it would have skipped. Follow-up instructions are recorded but never applied. New listeners start on Watch.
Manual — wait for my approval: the signal waits on the Dashboard under “Awaiting your approval” for 10 minutes, with “Trade it” and “Dismiss”, and the bell tells you. “Trade it” runs every check at that moment, with the current price, your limits and the trading switch. After 10 minutes it expires and nothing is placed. The waiting list survives a restart.
Auto — trade immediately: the signal goes through your rules and is placed within seconds. Switching to Auto asks you to confirm that orders will be placed on your account with no human check.
Even on Auto, some signals wait for you: one that looks like a repeat of a recent signal, one stopped only by “Max signals open at once” (with the button “Place anyway”), and one posted while the app was offline but still within “Max signal age (min)”.
Watch: “BUY XAUUSD 2400 SL 2390 TP 2410” arrives. Nothing is placed; the record says it would have opened 0.10 lots at market with stop-loss 2390 and take-profit 2410 (1% of 10 000 USD = 100 USD over a 10-dollar stop).
Manual: “SELL EURUSD 1.1000 SL 1.1030” arrives at 10:00. You click “Trade it” at 10:06, when the bid is 1.0985. The checks run at 1.0985. With a Max entry deviation of 0.10% (0.0011, about 11 pips from 1.1000), the 15-pip move is too far and the signal is skipped with that reason.
Manual: a signal arrives at 14:00 and you do not answer. At 14:10 it expires, shows as “Its time to be approved ran out: not traded.”, and nothing is placed.
A good order: start a new group on Watch to see how its signals would have done, move to Manual to confirm each one, and to Auto only once you trust it. A dry run shows the same in minutes, on the group's latest messages, whatever the mode.
On Manual the check runs when you approve, not when the signal arrived: after a few minutes the price may be far from the entry, and your rules may skip it.
Watch also blocks everything a signal left behind: follow-ups from a Watch listener never change trades, and a waiting limit of a listener switched to Watch never goes to market when it expires.
Signals read on Watch count toward your daily signals like traded ones.
Entry
Entry mode
Market enters right away at the current price. Limit places a pending order at the entry price stated in the signal and waits for the market to come to it. A limit waits only for the entry or a better price: a buy at the entry or lower, a sell at the entry or higher. When the price is already better, "If the price is already better" decides.
MarketLimit (at the entry or better)
When it applies
A Limit listener still enters at market when the signal states no entry price; there is nothing to rest the order on.
How it works, more examples and what to watch out for
Market enters right away at the current price: the ask for a buy, the bid for a sell. If the signal gives a range, the middle of the range is the entry the checks measure from.
Limit places a waiting order at the entry price the signal states and lets the market come to it. It rests at your broker with its stop-loss and take-profit, and fills even if the app is closed at that moment.
A Limit listener still enters at market when the signal gives no entry price. When the price has already passed the entry (you would get a better price than asked), no limit can rest there, and “If the price is already better” decides.
An unfilled limit is cancelled after “Cancel a limit or stop order not filled after”, and “If the limit order expires” decides whether it may still enter at market.
“BUY XAUUSD 2400” with the ask at 2403. Market: buys now at about 2403. Limit: a buy limit waits at 2400 and fills only if the price falls to 2400.
“SELL EURUSD now SL 1.1050 TP 1.0950”, no entry price. Both modes sell at market at the current bid.
Limit, “BUY XAUUSD 2400” with the ask at 2396: the price is already better than the entry. With the default of “If the price is already better” it buys at market at about 2396, never above 2400.
A waiting limit counts toward your open-position and lot limits from the moment it is placed, and the signal counts toward “Max traded signals per day” even if the limit never fills.
A message that calls itself BUY LIMIT or SELL LIMIT on a Market listener is read as an entry now; the signal's story notes it. Set Limit here to wait for the price.
On a netting account, or with one trade per signal, the exits of a Limit entry are placed only once the limit fills or goes to market.
Where in an entry range
When a signal gives an entry range (“BUY GOLD 2400–2405”), the limit waits at one price inside it. The best price (the low edge for a buy, the high edge for a sell) gets the best fill but is reached least often; the worst is reached first, so it fills most often; the middle sits between.
The best priceThe middleThe worst price, fills most often
When it applies
Limit entry only, and only for a signal that gives a range; a single entry price is used as it is.
Example
BUY GOLD 2400–2405 with the price at 2410: the best price waits at 2400, the middle at 2402.5, the worst at 2405.
How it works, more examples and what to watch out for
Some signals give an entry range instead of one price, such as “BUY GOLD 2400–2405”. A limit can rest at only one price, and this setting picks where inside the range.
The best price is the low edge for a buy and the high edge for a sell. It gives the best fill but the price reaches it least often. The worst price is the edge the price reaches first (the high edge for a buy, the low edge for a sell), so it fills most often. The middle sits between. The best price is the default.
A signal with a single entry price uses that price as it is, and a signal with no entry at all enters at market.
While the price is inside the range, the entry deviation check sees no distance at all; outside it, distance is measured from the nearer edge.
“BUY GOLD 2400–2405”, ask at 2410. Best price: a buy limit at 2400. Middle: at 2402.50. Worst: at 2405. If the price dips to 2403 and turns back up, only the worst-price limit filled.
“SELL EURUSD 1.1000–1.1010”, bid at 1.0990. Best price: a sell limit at 1.1010. Middle: 1.1005. Worst: 1.1000, reached first as the price rises.
Only for Limit entry. A Market listener always measures from the middle of the range.
The stop-loss stays where the signal put it, so the stop distance depends on where the limit rests: for a buy with its stop at 2395, it is 5.00 from 2400 but 10.00 from 2405. With risk sizing, the lots follow that distance, for the same money at risk.
Stop orders do not use this setting: a buy or sell stop given as a range waits at the edge the price reaches first.
Stop orders
When a signal says BUY STOP or SELL STOP, place it at your broker as a stop order at its entry: it waits until the price rises to a buy stop or falls to a sell stop, and enters then. Off, the app reads such a signal like any other entry.
When it applies
Whatever the entry mode. If the price is already at or past the level when the signal comes, it enters at market, within the entry deviation. A stop that has not filled after the waiting order expiry is cancelled, never turned into a market order: the price never got there. A buy stop and a sell stop in one message (a straddle) trade one side only unless you let both sides trade below. Needs the MetaTrader expert 1.19, which comes with this version.
Example
BUY STOP US30 44100 with the price at 44020: a buy stop waits at 44100 and enters if the price breaks up through it.
How it works, more examples and what to watch out for
Some groups post breakout orders: BUY STOP above the price, SELL STOP below it. With this on, such a signal is placed at your broker as a stop order at its level, with its stop-loss and take-profits. MetaTrader enters it when the price reaches the level, even if the app is closed then.
It works whatever the entry mode. When the signal arrives with the price already at or past the level, the breakout has happened: it enters at market, within “Max entry deviation”, and further than that it is skipped.
A stop not filled after “Cancel a limit or stop order not filled after” is cancelled. It never turns into a market order, whatever “If the limit order expires” says: the price never got there.
A buy stop and a sell stop in one message (a straddle) trade one side only, unless you turn on “Let both sides of a straddle trade”. Off, the app reads BUY STOP and SELL STOP like any other entry.
“BUY STOP US30 44100 SL 43950 TP 44400” with the ask at 44020. A buy stop waits at 44100. The price rises through 44100: it enters there. If the price never gets there within 30 minutes (the default expiry), the order is cancelled.
Same signal, ask already at 44120 when it arrives. The breakout has happened, so it buys at market at about 44120. With a Max entry deviation of 0.05% (about 22 points from 44100) that is within range and it enters; at 44150 it would be skipped.
Off: “SELL STOP XAUUSD 2390” with the bid at 2400 is read as a plain sell at 2390. A Market listener measures 10.00 from the entry and, with a deviation set, usually skips it; the signal's story notes that the message was a stop order.
“SELL … STOP LOSS 2420” is a stop-loss, not a stop order. Only an order called buy stop or sell stop counts.
A waiting stop counts toward your open-position and lot limits until it fills or is cancelled, and a follow-up such as “cancel the pending” or “move SL” acts on it as on a waiting limit.
Dry runs play stop orders too: a buy stop fills when the price rises to it, a sell stop when it falls to it.
Let both sides of a straddle trade
A straddle is a buy stop above the price and a sell stop below it in one message, so the trade follows whichever way the price breaks. Off, only the first side to enter trades: the moment it fills, or enters at market because the price was already past it, the app cancels the other side's stop, and an order of that message the other way that comes after is refused. On, each side waits on its own and both can fill.
When it applies
Only with Stop orders, and only for the stops of one message on this listener: two separate messages are two separate trades. Stops the same way as the side that entered keep waiting.
Example
BUY STOP US30 44100 and SELL STOP US30 43900 with the price at 44000. The price rises to 44100: the buy enters and the sell stop at 43900 is cancelled. With this on, the sell stop stays, and a fall to 43900 later opens the sell too.
How it works, more examples and what to watch out for
A straddle is a buy stop above the price and a sell stop below it in the same message, so the trade follows whichever way the price breaks out.
Off (the default), only the first side to enter trades. The moment one side fills, or enters at market because the price was already past it, the app cancels the other side's stop at your broker. A later order of the same message in the other direction is refused.
On, each side waits on its own as a separate stop order, and both can fill. Nothing is cancelled or refused.
Only the stops of one message on this listener are linked. Two separate messages are two separate trades. Stops in the same direction as the side that entered keep waiting.
“BUY STOP US30 44100 / SELL STOP US30 43900”, price at 44000. Off: the price rises to 44100, the buy enters and the sell stop at 43900 is cancelled; the signal shows it as “cancelled: the other side of the straddle filled”.
Same message, on: the buy enters at 44100, the sell stop stays. Later the price falls to 43900 and the sell opens too. You now hold both a buy and a sell on US30, each with its own stop-loss.
Shown only with “Stop orders” on.
With both sides on, a price that swings through both levels opens two opposite trades. Each counts toward your open-position and lot limits, and both may end at their stop-loss.
The link between the two sides holds after an app restart too, and dry runs play a straddle the same way: with this off, the side that entered first trades and the other is shown as cancelled.
Cancel a limit or stop order not filled after
A limit or stop order that waits at your broker and has not filled after this many minutes is cancelled. A signal waiting for your approval is not an order yet: it waits 10 minutes, whatever is set here.
When it applies
With Limit entry, with Stop orders, when a Market listener waits at the entry because the price already passed a take-profit, and when you place a signal by hand as a limit. Orders placed before a restart keep their clock.
How it works, more examples and what to watch out for
A waiting limit or stop order that has not filled after this many minutes is cancelled. The default is 30.
About every 30 seconds the app looks for orders past their time. A cancelled limit then follows “If the limit order expires”: it is cancelled for good, or it may still enter at market if the price is close. A cancelled stop order, or a limit waiting for the price to come back to an entry it had passed, is always just cancelled.
The clock runs from the moment the order was placed. After an app restart, orders keep their original time and are checked with the listener's current setting.
A signal that waits for your approval (Manual mode) is not an order yet and has its own wait of 10 minutes; these minutes start counting once an order is placed.
Expiry 30. A buy limit on XAUUSD at 2400 is placed at 09:00 with the ask at 2405. By 09:30 the price has not come down to 2400, so it is cancelled at about 09:30 (within 30 seconds).
Expiry 120 for a slow swing group: a sell limit on EURUSD at 1.1050 placed at 10:00 may fill until 12:00.
You close the app at 10:10 with a limit placed at 10:00 and expiry 30, and reopen it at 11:00. The order is already past its 30 minutes and is handled at once.
The order rests at your broker, so while the app is closed nothing cancels it: it may fill after its time and is only handled once the app is running again.
Until it fills or is cancelled, a waiting order counts toward your open-position and lot limits. A long expiry can hold those places for hours.
An order you delete by hand in MetaTrader is marked cancelled.
If the limit order expires
What to do when the pending order expires unfilled: cancel it, or enter at market instead, but only while the price is still within the entry deviation below. The market entry is placed only while your other rules still allow a new trade.
Cancel itEnter at market if still close
When it applies
Only with Limit entry.
How it works, more examples and what to watch out for
What happens when a waiting limit expires unfilled.
“Cancel it” (the default): the order is cancelled and the trade is shown as unfilled.
“Enter at market if still close”: after cancelling, the app checks the price against “Max entry deviation”, measured from the limit price, or from the range when the signal gave one. Within it, a market order goes out with the same lots, stop-loss and take-profit, and keeps its place in the signal.
The market order must still pass the rules a new trade passes, as they are now: the listener still on and not on Watch, trading hours and days, daily loss, open-position and lot limits, spread, margin and the trading switch. The daily signal count is not checked again, because the signal counted when its limit was placed. If a rule refuses, the order stays cancelled and the signal's story names the rule.
Buy limit on XAUUSD at 2400, deviation 0.10% (2.40). It expires with the ask at 2401.80: 1.80 away, within range, so it buys at market at about 2401.80 with the same stop and take-profit.
Same order, the ask at 2406 when it expires: 6.00 away, more than 2.40. No market order; the limit stays cancelled.
Within range, but the group already lost 250 today against its own Max daily loss of 250. The market order is refused, and the signal's story gives the daily-loss reason.
With “Max entry deviation” at 0 (off, the default for a new listener), the “still close” check never trips: an expired limit goes to market wherever the price is. Set a deviation if “still close” should mean something.
The market order is not sized again: it keeps the lots, stop-loss and take-profit the limit had. It uses your “Max slippage (points)”, or the listener's own if it has one.
Only for Limit entry. Stop orders are never sent to market when they expire.
If the price is already better
A limit waits on the far side of the market. When the signal's entry is already past the current price — you would pay less than asked — no limit can rest there. Enter at market instead, never worse than the entry, or skip the signal.
Enter at market, never worse than the entrySkip the signal
When it applies
Limit entry only, and only while the price is within the entry deviation; further than that the signal is skipped as a runaway. The market order's allowed slippage is capped at the distance to the entry, so the broker refuses any fill worse than it.
Example
BUY GOLD @ 2400 with the ask at 2395: Enter at market fills at 2395, capped at 2400; Skip records the signal and does nothing.
How it works, more examples and what to watch out for
A buy limit waits below the price and a sell limit above it. When the signal arrives and the price has already passed its entry in your favour (a buy with the ask below the entry, a sell with the bid above it), a limit cannot rest there.
“Enter at market, never worse than the entry” (the default): the app first checks “Max entry deviation”; too far is skipped as a runaway. Within range, it sends a market order whose allowed slippage is capped at the distance to the entry, so your broker refuses any fill worse than the entry. The spread check applies.
“Skip the signal”: the signal is recorded as skipped, with the reason that the price is already better than the limit, and nothing is placed.
“BUY XAUUSD 2400” with the ask at 2395. Enter at market: it buys at about 2395, and a fill above 2400 is refused by the broker. Skip: recorded, nothing placed.
“SELL EURUSD 1.1000” with the bid at 1.1025, deviation 20 pips. The price is 25 pips past the entry, more than 20: skipped even with Enter at market.
Only for Limit entry. A price that has passed the entry by a lot often means the move already happened; the deviation check is what stops you taking it late, and it is off at 0.
When the entry and the price are less than one point apart, the slippage allowed is 0 and the broker may refuse the fill.
Stop orders work the other way: a price already past a stop's level means the breakout happened, and the stop enters at market within the deviation.
Max entry deviation
Skip the signal if the price has already moved further than this from the stated entry, in either direction; you would be chasing. A signal with no stated entry is never checked.
When it applies
Checked on Market entries, and on a Limit that turns into a market order: one that expired and may enter at market, or one whose entry the price has already passed. Measured in the unit below.
Example
Stated entry 52 500 on US30, price now 52 580 (0.15% away): skipped with the default 0.10%, taken with 0.25%. In pips: entry 1.1000, price 1.1030 (30 pips away): skipped with 20, taken with 50.
How it works, more examples and what to watch out for
If the price has already moved further than this from the signal's entry, in either direction, the signal is skipped: you would be chasing. “Off” is how a new listener starts.
It is measured from the current price: the ask for a buy, the bid for a sell. With a range, a price inside it has no deviation and a price outside is measured from the nearer edge. A signal with no entry price is never checked.
It applies to Market entries, to a stop order whose level the price has already passed, and to a Limit that turns into a market order: one that expired with “Enter at market if still close”, or one whose entry the price has already passed.
The unit is set by “Deviation unit”: a percent of the entry price, or pips. Percent may be 0–10, pips 0–5000.
Percent 0.10. “BUY XAUUSD 2400”, ask at 2408.50: 8.50 away = 0.35%, more than 0.10% (2.40): skipped. At 2401.50 (0.06%) it enters.
Pips 20. “SELL EURUSD 1.1000”, bid at 1.0970: 30 pips away, more than 20: skipped. With 50 it enters.
Percent 0.10 on US30 with the entry at 42 000: the allowed distance is 42 points. At 42 030 it enters; at 42 060 it is skipped.
With “Off” nothing is ever skipped for chasing, and an expired limit with “Enter at market if still close” goes to market wherever the price is.
Too tight a value skips good signals on a fast market or when an approval takes a few minutes; on Manual the check runs when you click “Trade it”.
The skip reason gives the price, the distance and your setting, for example “The price 2408.5 is already 0.35% from the signal's entry 2400, more than this listener's Max entry deviation (0.1%).”
Deviation unit
Percent is relative to the entry price and the default: it means the same on every instrument, indices and crypto included, where a pip means little. Pips is a fixed price distance, the traditional measure on forex and metals.
PipsPercent of price
Example
On forex a pip is 10 points on 3- and 5-digit symbols; on gold it is 0.10 and on silver 0.01. 20 pips = 0.0020 on EURUSD and 2.00 on gold. 0.5% is about 55 pips on EURUSD at 1.10 and about 12 dollars on gold at 2400.
How it works, more examples and what to watch out for
Sets how “Max entry deviation” is measured.
Percent of price is relative to the entry price. It means the same on every instrument, so one value works across forex, gold, indices and crypto. It is the default for a new listener.
Pips is a fixed price distance, the usual measure on forex and metals. A pip is 0.0001 on 5-digit forex pairs and 0.01 on JPY pairs, 0.10 on gold and 0.01 on silver, and 1.0 of the price on indices such as US30 or NAS100 and on bitcoin and ether.
20 pips is 0.0020 on EURUSD, 0.20 on USDJPY, 2.00 on gold, 20 points on US30 and 20 dollars on BTCUSD.
0.5% is about 0.0055 (55 pips) on EURUSD at 1.10, 12 dollars on gold at 2400, 210 points on US30 at 42 000 and 420 dollars on BTCUSD at 84 000.
Changing the unit does not convert the number: 20 in pips becomes 20% in percent, which the app refuses (the percent range is 0–10). Set the value again after switching.
On a listener that trades both forex and indices, pips mean very different distances: 20 pips is 0.0020 on EURUSD but 20 points on US30. Percent avoids that.
A listener saved by an old version without a unit reads as pips.
If the price already passed a take-profit
A signal can arrive after the price already went through its first take-profits. Skip it, open the trade now with only the take-profits still ahead, or wait at the entry, with every take-profit, for the price to come back.
Skip the signalTrade the take-profits still aheadWait for the price to come back to the entry
When it applies
Market entry only, and only while the price is within Max entry deviation; further than that the signal is skipped as a runaway. With every take-profit passed there is nothing ahead to trade, and only waiting helps.
Example
SELL GOLD 4172–4180, SL 4184, TPs 4170 / 4168 / 4166, arriving with the price at 4167.53: Skip does nothing; the take-profits still ahead sell now with 4166 only; waiting places a sell limit at 4172 with all three.
How it works, more examples and what to watch out for
What a signal does when it arrives with the price already through one or more of its take-profits: a buy with the ask at or above TP1, a sell with the bid at or below it.
“Skip the signal” (the default): nothing is placed, and the signal's story names the take-profit the price had passed.
“Trade the take-profits still ahead”: the trade opens at market with the take-profits the price has not reached yet. Each keeps its number and its share of the size (tp3 stays tp3), and the passed ones are listed as not placed. The stop-loss is the signal's, so the risk is the same while the targets are closer than the signal planned. With every take-profit passed, the signal is skipped.
“Wait for the price to come back to the entry”: the entry rests as a limit where the price meets the entry first on its way back, the edge of the entry zone nearest to it or the entry when the signal gave one price, with every take-profit and the signal's stop-loss. It waits for “Cancel a limit or stop order not filled after”, then is cancelled; it never turns into a market order.
“Max entry deviation” is checked first either way: a price further than that from the entry is skipped as a runaway.
SELL GOLD 4172–4180, SL 4184, TPs 4170 / 4168 / 4166 / 4163, the bid at 4167.53: 4170 and 4168 are passed. Trade the take-profits still ahead sells now with tp3 4166 and tp4 4163; tp1 and tp2 are listed as not placed.
Same signal, waiting: a sell limit at 4172, the zone's lower edge, with all four take-profits. The price comes back to 4172 within the expiry: it sells there, with every target ahead. The price keeps falling: the order expires and nothing is traded.
Symbols
Symbols
Only trade these symbols from this group. Empty = all symbols the global whitelist allows. Write each one as the Signals page shows it (XAUUSD for gold) or as your broker spells it (XAUUSD.s), separated by commas.
How it works, more examples and what to watch out for
Only signals on these symbols are traded from this group. Empty means every symbol your profile's “Allowed symbols” allows.
Write each one as the Signals page shows it (XAUUSD for gold), as the group writes it (GOLD), or as your broker spells it (XAUUSD.s), separated by commas. The app reads each entry the way it reads a signal's symbol, so any of these spellings matches.
The list narrows the whitelist, never widens it: a symbol must be allowed by both. A signal on any other symbol is skipped with a reason that names the list.
Symbols “XAUUSD, XAGUSD”. “BUY GOLD 2400” trades; “SELL EURUSD 1.1000” is skipped: this listener only trades XAUUSD, XAGUSD.
Listener symbols “EURUSD, GBPUSD”, profile whitelist “EURUSD, XAUUSD”. EURUSD trades; GBPUSD is skipped by the whitelist, even though the listener lists it.
A group posts gold, forex and US30, and you only want its gold calls: set “XAUUSD” here, and use another listener with “Settings of its own” if the rest should trade differently.
Only one listener takes each message. A second listener on the same chat does not get the symbols the first one skips: the first takes the message and skips it. To split a group by symbol, use topics if it has them, or one listener with its own settings.
A skipped signal still counts toward your daily signals: it was read as a signal.
The symbol names map (“Symbol names at your broker”) turns the group's words into tickers first, so a group's “GOLD” matches XAUUSD here.
Settings of its own
Settings of its own
Any of the profile's trading settings, set differently for this group's signals: its own size (risk %, fixed lots or cash), how its take-profits are traded and trailed, its runners, its stop-loss rules, its spread and slippage limits, the days and hours it trades. And limits of its own: the profile's daily, open-position and lot limits counted on this group's trades only, such as a daily loss of 250 for this group within the profile's 500. Whatever is not set here follows the profile, and changes when the profile changes.
When it applies
A limit of its own counts only this group's trades and is never above the profile's: both apply, and whichever is reached first stops. When the profile's limit is reached every group stops, since it counts them all. A limit above the profile's is refused, and so is lowering the profile's below a group's own. What belongs to the account's money as a whole (margin use and the equity floor) and duplicate signals stay the profile's alone.
Example
Profile: 1% risk and a daily loss of 500. A gold group: fixed lots 0.05, trading 08:00-17:00, its own daily loss 250. After the gold group loses 250 today it stops; the others trade on until the whole profile reaches −500.
How it works, more examples and what to watch out for
By default a listener trades with the profile's settings. Here you give it values of its own for any of them. Pick a setting from “Add a setting of its own…”: it starts at the profile's current value, with the profile's value shown under it. Change it: it is saved by itself. ✕ removes it, and the listener follows the profile again. What you do not set here follows the profile and changes when the profile changes.
What a listener can set for itself: its size (“Sizing mode”, “Risk % of equity”, “Fixed lots are for”, “Fixed lots”, “Fixed cash”, “Max lots per signal”); take-profits and trailing (“Multiple take-profits”, “Share across take-profits”, “Trailing stop”, “Pips behind the take-profit”, “Max take-profits per signal”, “Require full signal”); all runner settings; stop-loss rules (“Require stop-loss”, “Own stop-loss”, “Own stop-loss (pips)”, the older default stop); “Max spread (points)” and “Max slippage (points)”; “Trading days” and “Trading hours”; and the group's follow-ups (“Exits and stop moves”, “Partial closes and target moves”). These replace the profile's value in either direction: a listener may risk 2% while the profile risks 1%.
Limits of its own are different. Nine profile limits can be set per listener: “Max traded signals per day”, “Max daily loss”, “Daily profit target”, “Max open positions”, “Max open positions per symbol”, “Max signals open at once”, “Max total lots”, “Max lots per symbol” and “Pause between signals (seconds)”. A listener's own counts only its own trades, and can only be tighter: at most the profile's (a cooldown may be longer). Both apply, and whichever is reached first stops.
When the listener's own limit is reached, only this listener stops; the others trade on. When the profile's limit is reached, every listener stops, this one included, because the profile counts them all.
Some settings stay the profile's alone, because they belong to the account as a whole: “Max margin use %”, “Lowest equity to trade”, duplicates, “Max signal age (min)”, the symbol whitelist and names, and “Trading enabled”.
Double size for one group. Profile: 1% risk. 10 000 USD equity and a 20-pip stop on EURUSD give 0.50 lots. The listener's own “Risk % of equity” 2 gives 1.00 lots; its own 3% would give 1.50, capped at the profile's “Max lots per signal” of 1.00 unless the listener sets its own.
A gold group on fixed lots in the London session. Profile: 0.5% risk, all day. The listener's own “Sizing mode” Fixed lots with 0.05 lots, and “Trading hours” 08:00-17:00 (broker time). Its gold signals open 0.05 lots per take-profit, and one at 18:30 is skipped as outside trading hours; every other listener still sizes by 0.5% around the clock.
A daily loss of its own. Profile “Max daily loss” 500, the gold group's own 250, the forex group with no limit of its own. The gold group closes −90 and −170 (net −260): it stops for the day, and the forex group trades on. If the forex group then loses 240, the profile reaches −500 and every group stops.
A limit above the profile's. Profile “Max open positions” 10; typing 12 as a listener's own is refused: its own limit can never be above the profile's. Lowering the profile's to 3 while a listener has its own 5 is refused the same way.
Set the profile's limits with each group's own in mind. A listener's own “Max open positions” of 5 can still stop at 2 when the other listeners have filled the profile's limit.
A setting of its own may be 0 or empty and still count: a “Max spread” of 0 turns the spread check off for this listener only, and empty “Trading hours” trade around the clock. A limit of its own must be above 0; remove it to have none.
Its own values must work together with the profile's. A listener's own runner unit different from the profile's needs its own start and trail, and a trail must stay smaller than the start. A save that breaks a rule is refused with the reason.
An open listener counts them beside “Settings of its own”, for example “3 own settings”, and the website shows the full rules a listener trades with.
Application
Launch at startup
Starts Relay2Trade automatically when you sign in to Windows, so signals are not missed after a reboot.
When it applies
Keep it on (the default) on the computer or VPS that trades.
Example
Windows installs an update overnight and restarts: when you sign in, the app starts in the tray and the listeners reconnect.
How it works, more examples and what to watch out for
On, the app adds a startup entry for your Windows user. It runs when that user signs in to Windows, not when the machine powers on.
The app checks the entry at every start and repairs its path if the app moved. Turning the setting off removes the entry at once.
Whether that automatic start shows the window depends on Start minimized in tray.
It belongs to this computer and is not synced to your account.
On, with Start minimized in tray on: after a restart and sign-in, the app is in the tray and trading within seconds; no window opens.
Off: after a restart nothing trades until you open Relay2Trade yourself.
On a VPS that restarts for updates: on is not enough by itself. Windows must also sign the user in automatically, or nothing starts until you connect with Remote Desktop.
On a VPS, set Windows to sign in by itself after a restart; the VPS guide on the website shows how. Without it the app waits for someone to sign in.
MetaTrader 5 is started by the app for each trading profile, so it does not need its own startup entry.
Start minimized in tray
Decides whether the automatic start with Windows opens hidden in the tray or with the window showing.
When it applies
Keep it on (the default) for a quiet start. Opening the app yourself always shows the window.
Example
On: after a reboot the app runs in the tray and you open it from the tray icon when you want to look.
How it works, more examples and what to watch out for
It applies only to the start from Launch at startup. With Launch at startup off it has no effect.
On, the app starts with no window and no splash screen; listeners, MetaTrader and trading start as usual. Off, the window opens as if you had launched it.
Launching the app from the desktop or the Start menu always shows the window. It belongs to this computer and is not synced.
On: the PC restarts at 03:00 for updates; the app comes back in the tray and a EURUSD signal at 03:10 is placed with no window open.
Off: after every sign-in the window opens on the dashboard, so you see at once whether MetaTrader and Telegram are connected.
Hidden does not mean stopped: the app trades from the tray. Use Quit in the tray menu to stop it.
Keep running when window closes
Yes: the ✕ button hides the window to the tray and trading continues. No: closing the window quits the app and stops trading.
When it applies
Keep it on (the default) so a reflexive ✕ never stops trading.
Example
On: you close the window after checking a trade; the app keeps listening and places the next XAUUSD signal.
How it works, more examples and what to watch out for
On, ✕ only hides the window. Listeners, MetaTrader and trading keep running, and you bring the window back from the tray icon or by launching the app again.
Off, ✕ quits the whole app, the same as Quit in the tray menu: every profile stops, listeners disconnect and the profiles' own MetaTrader copies close. Positions stay open at the broker with their stop-loss and take-profit.
A change applies to the next ✕, without a restart. It belongs to this computer and is not synced.
On: you close the window at 10:00; a US30 signal at 10:20 is placed as usual.
Off: you close the window at 10:00; the US30 signal at 10:20 is missed, and the trailing and follow-ups of trades already open stop until you open the app again.
With it off, closing the window also stops the app's work on open trades: trailing stops, runners and follow-up messages. Only what is already at the broker (stop-loss, take-profit) keeps working.
If the app keeps running after you close it, this is why. Use Quit in the tray menu to stop it on purpose.
Show tips
A short tip at the bottom of the window from time to time, about something the app can do, with “Show me” to where it is.
When it applies
Turn it off once you know the app well.
How it works, more examples and what to watch out for
On, a line at the bottom of the window shows one tip at a time, picked at random, and a new one every few minutes. Tips come from our server, so new ones appear without an update.
A tip about something you already set up, like starting with Windows when it is already on, is skipped. You see every tip once before any comes back.
“Show me” opens the page or setting the tip is about. › shows the next tip; ✕ hides the line until the next one.
It belongs to this computer and is not synced to your account.
On: a tip says “To the entry” moves your stop to the entry; “Show me” opens Settings at that option.
Off: the line at the bottom is gone; everything the tips talk about is still in Help.
Log level
How much detail goes into the app's technical log file.
debuginfowarnerror
When it applies
info is right for everyday use. Use debug only while chasing a problem or when support asks.
Example
A group's messages never show up: set debug and the Activity filter to Everything (debug) to see messages dropped as not a signal.
How it works, more examples and what to watch out for
debug records everything, info (the default) records normal events and problems, warn only warnings and errors, error only errors.
The change applies at once, without a restart. The log file is capped at 5 MB, after which it starts a new one and keeps one older file.
A support ticket sent with the log attached carries the last part of this file, so the right level helps support see what happened.
It belongs to this computer and is not synced.
info: a Telegram sign-in error is logged as a warning with its full technical text, enough for a ticket.
debug for an hour on a busy group: the file fills faster and older lines roll into the old file sooner.
Set it back to info after debugging; debug makes the file roll over quickly, and the lines that matter for a ticket can be pushed out.
warn and error hide normal events, which makes a problem harder to trace.
Language
The language of the whole app: pages, notices, the reasons given for each signal and status messages.
EnglishRomânăPortuguês (Brasil)EspañolTiếng ViệtРусскийFrançaisTürkçeBahasa Indonesiaالعربيةไทยहिन्दीPolski
When it applies
Pick the one you read most easily; it does not change how signals in any language are read.
Example
Română: the dashboard, the bell and the reason a signal was skipped appear in Romanian.
How it works, more examples and what to watch out for
Each language is listed in its own words. The change applies as soon as you pick it, without a restart.
It follows your account: the same language on every computer and on the website's view of the app. The newest change wins, wherever it was made.
It has nothing to do with the signals. A group posting in English, Romanian or any other language is read the same way.
You switch to Română on your laptop; the VPS app picks up the same language at its next check with the server, within about 10 minutes.
Language English, group posting "CUMPĂRĂ XAUUSD 2400 SL 2390": the signal is read normally and its story is shown in English.
If the language changes by itself, it was changed on another computer or on the website; the newest change wins.
The tray menu takes the new language the next time the app starts.
MetaTrader link
How the trading bridge inside MetaTrader 5 talks to the app: a named pipe, or a local socket on 127.0.0.1.
Named pipe (recommended)Local socket (needs an allowed URL)
When it applies
Keep Named pipe (recommended). Switch to Local socket only if support asks you to.
Example
Named pipe: after installing, MetaTrader connects with nothing to set in its options.
How it works, more examples and what to watch out for
Named pipe (recommended), the default: works out of the box. The app allows the needed permission on the bridge's chart only; MetaTrader's terminal-wide setting stays off.
Local socket: the bridge connects to 127.0.0.1 and works only after 127.0.0.1 is on MetaTrader's allowed-URL list. In each MetaTrader: Tools › Options › Expert Advisors, tick "Allow WebRequest for listed URL", add 127.0.0.1, OK. The app cannot write that list for you.
Changing it redoes the setup of every profile's MetaTrader, so each restarts once. The status bar shows which link is in use.
It follows your account: every profile, every computer.
Two profiles, switched to Local socket without the allowed URL: both terminals restart, the app keeps waiting for them to connect, and a yellow notice explains the missing step.
Local socket with 127.0.0.1 added in every MetaTrader, then Fix MT5 connection: the bridge connects and the status bar reads "socket".
Back to Named pipe: each MetaTrader restarts once and connects with nothing to set.
The socket needs the allowed URL in every MetaTrader, including one added later or on another computer, because the setting follows your account.
Switching restarts every profile's MetaTrader once. Open positions are not touched.
Remote control
The master switch for the Desk on relay2trade.com. On, the app sends its status, signals and settings there over a connection it opens itself, and carries out what you do there.
When it applies
Keep it on (the default) to watch the app from your phone and to change settings from the website.
Example
On: from your phone you turn Trading enabled off in the Desk, and the app stops opening trades within seconds.
How it works, more examples and what to watch out for
Nothing can reach your computer from outside: the app opens the connection itself, sends over it, and takes what you do in the Desk over it, within seconds while it runs.
The three switches below decide what is sent; with this one off, none of them sends anything and nothing done on the website reaches the app.
The switch follows your account, like the language.
On, Sync activity on: you see on your phone that a XAUUSD signal was placed at 2400 with 0.50 lots, and why another was skipped.
Off: the website shows the app as online (the licence check still runs every 10 minutes) but no signals, and any edit made there is not applied.
Some things are sent whatever the switches say: the licence check with each profile's status, dry-run results without message text, error reports and support tickets.
On a new computer the app takes your settings from your account at sign-in, whatever this switch says.
Sync activity
Sends each profile's MetaTrader and Telegram status, the signals as the app read them, and the activity lines, so you see them on the web and mobile dashboard.
When it applies
Keep it on (the default) to follow your trades away from the computer. Needs Remote control on.
Example
On: you open the website on your phone and see that the EURUSD signal at 1.1000 was placed and the GBPUSD one was skipped for the daily limit.
How it works, more examples and what to watch out for
Changes are sent in batches a few seconds after they happen. A failed send is kept and retried, waiting longer each time, up to 5 minutes between tries.
The original message text goes only when Sync original messages is also on. Dry-run records are never sent.
Turning it on also sends the latest 200 signals, so the dashboard is not empty.
On: a US30 signal at 42 000 is placed; a few seconds later it shows on the website with its lots, stop-loss and take-profits.
Off: the website shows only that the app is online. For levels and seasons the app sends a counts-only day report about once an hour instead.
With it off, support cannot see your signals when you ask why one was skipped; attach the app log to the ticket instead.
Sync original messages depends on this switch.
Sync settings & listeners
Backs up each profile's settings and listeners to your account, for a new computer or a reinstall, and so they can be edited from the website. Credentials and sessions never sync.
When it applies
Keep it on (the default). Needs Remote control on.
Example
New VPS: you install the app, sign in, sign in to Telegram again, and every profile and listener is back as it was.
How it works, more examples and what to watch out for
The app sends the trading switch, the risk settings, the symbol rules and the listeners of each profile: at every start, after each change to them, and after your plan held a setting.
The website's editor shows this copy. An edit made there is checked by the same rules as on the desktop and applied by the app; an edit that fails a rule is not applied at all, and the bell says why.
Passwords, the Telegram session, MetaTrader paths and bridge secrets are never in it.
You change Risk % of equity from 1 to 0.5 on the desktop; the website shows 0.5 a few seconds later.
Off: edits on the website are not applied, and a reinstall on a new computer starts from whatever copy was last sent.
At sign-in on a new computer the app takes the settings from your account, not from the fresh install, so defaults never overwrite settings made elsewhere.
Sync original messages
Also sends the original text of each signal message, so the website and our support can show it next to what the app understood.
When it applies
On (the default) helps put right a message the app read wrong. Turn it off if you prefer that your groups' text stays on this computer. Needs Sync activity on.
Example
On: a message read with the wrong stop-loss shows on the website with its original text, so support can see the mistake.
How it works, more examples and what to watch out for
On, the message text is stored with the signal in your account on our servers. It comes from your signal groups, which may be private or paid.
Off, only the parsed fields leave this computer: symbol, side, entry, stop-loss, take-profits and the result.
It works only with Remote control and Sync activity both on.
On: the group posts "GOLD buy now 2400, SL 2390, TP 2410/2420"; the website shows this text above the parsed signal XAUUSD buy, SL 2390, TP 2410 and 2420.
Off: the website shows XAUUSD buy, SL 2390, TP 2410 and 2420, but not the words the group used.
Dry runs never send message text, whatever this switch says.
Tell me when the app goes quiet
If your app stops answering for about 15 minutes (it crashed, the computer went to sleep or offline, or it was closed), you get a notice here. If it is still off a day later you get an email, and at most two more, a day apart. Only while your plan is active.