Alerts & notifications

Atlaas can tell you when something happens on a terminal: an alert raised by your own EA, a copy-trading failure, an order placed or closed, a state change (running, stopped, error), an EA deployment finishing or failing, or the live-vs-backtest monitor flagging decay or slippage.

Channels

A channel is a named place notifications go. Create as many as you like in Settings → Notifications and give each one a name; you then pick channels wherever events come from.

Types whose provider is not configured on a deployment (Telegram, Pushover, browser push, the Twilio ones) are not offered. Credits for a paid message are reserved before it is sent and released if the provider refuses it; an account without enough credits gets no message, and that never turns the channel off.

SMS, WhatsApp and calls cost money per message, so they come with limits:

• Solo plan and above, and only numbers in the countries the deployment allows (NOTIFY_PHONE_COUNTRIES, comma-separated dialling codes, default +91).
• At most 3 numbers waiting for confirmation at once.
• Confirmation codes (SMS, calls and MT5 push): 5 a day per account, 3 a day per number or MetaQuotes ID whichever account asks, and a minute apart. A code allows 5 wrong tries.

Every account starts with an Org members email channel. A channel whose destination is gone (a deleted Discord webhook, a bot removed from the chat) or that fails 10 times in a row turns itself off, and every member gets an email saying so. Send test on any channel posts a test message and shows the result.

Delivery settings per channel

Open a channel in Settings → Notifications to set how it delivers:

Where events go

Events are grouped, and each group can be sent to channels from four places:

• Account default (Settings → Notifications): where a terminal's events go until you pick channels on that terminal.
• Terminal (the Notifications card on its Overview tab): a switch per group decides which events the terminal sends, and a channel picker next to it decides where. The switches default to EA alerts and Failures on, Trades and Terminal state off.
• Strategy: its signals, trades and failures, from every terminal it trades on. Atlaas matches the trade's magic number (for a close, the magic of the position's opening deal) to the strategy.
• EA deployment: that chart's alerts (matched by the alert's chart symbol and timeframe), trades and failures (by its magic number), deployment status and monitor verdicts.

Account risk limits are set per terminal on its Notifications card, each optional:

Each limit sends one alert per crossing, not one per heartbeat. Deposits and withdrawals move the day's starting point and the peak with them, so they never read as profit or loss. Changing a limit starts that limit over; the others keep their state. Risk alerts are errors, so they come through quiet hours and bundling.

When several of these match one event, it goes to all of them and each channel gets it once: a Gold Scalper trade on terminal XAU-Live-01 reaches the strategy's channels and the terminal's.

Alerts also appear in the Logs page under the Alerts category and in GET /v1/events?category=alert.

Send an alert from your EA

Print a line that starts with ATLAS_ALERT to the Experts log. The runner already tails that log, so nothing else is needed on the terminal. Either form works:

ATLAS_ALERT RSI crossed 70 on EURUSD
ATLAS_ALERT {"message":"RSI crossed 70","symbol":"EURUSD","price":1.0852,"level":"WARN"}

A helper you can paste into any MQL5 program. It escapes quotes and backslashes, which would otherwise break the JSON and turn the whole line into a plain-text alert:

void AtlasAlert(string message, string level = "INFO", double price = 0)
{
   StringReplace(message, "\\", "\\\\");
   StringReplace(message, "\"", "\\\"");
   Print("ATLAS_ALERT {\"message\":\"", message, "\",\"symbol\":\"", _Symbol, "\",\"level\":\"", level,
         "\",\"price\":", DoubleToString(price, _Digits), "}");
}

Use Print. MT5's Alert() and SendNotification() don't create Atlaas alerts. In a backtest the lines stay in the tester's log.

Alerts reach Atlaas within about 2 seconds of the Print. A line that repeats with the same timestamp and message (the runner re-sends the log tail after a reconnect) is recorded once.

Set up Telegram alerts

1. In the portal open Settings → Notifications, press Add channel, choose Telegram and name the channel. If Telegram is greyed out, this deployment has no bot.
2. Open the link it shows. For a private chat, Telegram opens the bot with a Start button; press it. For a group, the second link lets you pick the group and adds the bot to it, which sends the same start command there.
3. Back in the portal press I pressed Start. Atlaas looks for your start message, records the chat it came from, and shows its name. The link is valid for 10 minutes; Finish connecting on the channel gets a new one.
4. Tick the groups it should get as the account default, or pick it on a terminal, strategy or EA. Send test posts "Atlaas is connected to …" to confirm.

Repeat for every chat or group you want; each is its own channel. The chat id is never typed in: it is taken from the start message the bot received, which proves the chat is yours. Telegram broadcast channels cannot be connected this way; use a group. Move to another chat on a channel re-runs the handshake; Delete removes it everywhere it was picked.