Overview
Risk rules watch the live telemetry your Reporter EA streams from each MetaTrader 5 terminal. Every time a fresh snapshot arrives, xTriel checks your saved limits for that account. When a tracked metric crosses a limit you set — daily drawdown, profit target, floating loss, or a terminal that stopped reporting — xTriel fires an alert.
xTriel evaluates rules against the read-only snapshots it receives — it does not open, close, or modify positions. If a limit trips, you get a warning; acting on it is up to you and your trading setup.
Because rules run server-side against incoming snapshots, alert timing follows how often the EA reports. With the default UpdateTimer of five seconds and a 60-second heartbeat, a breach is normally caught within a few seconds of the snapshot that shows it.
Risk rule types
Rules apply per account and are set on the Risk page. Core limits sit at the top of each account card; the rest live under More limits. Below are the checks this guide focuses on.
| Rule | Trips when | Use it for |
|---|---|---|
Max daily drawdown | The account's drawdown percent for the day reaches your limit. | A per-account daily loss guardrail — the most common prop-firm and personal rule. |
Profit target | The account's daily profit percent reaches or exceeds the value. | Getting a heads-up when a target is hit so you can lock in or stand down. |
Max floating loss | Open, unrealized loss reaches the dollar value you set. | Watching live exposure before positions close and losses become realized. |
Stale-data / heartbeat | No snapshot arrives for the number of minutes you set. | Catching a frozen terminal, a dropped VPS, or a network issue — the EA's heartbeat should keep a healthy account fresh. |
The More limits panel carries additional checks alongside these, including percent-based max drawdown, a minimum-equity floor, and a max-open-positions cap. Any field you leave blank is simply not evaluated for that account.
Set rules per account
Rules are configured per account, so you can run tight limits on a prop-firm challenge and looser ones on a personal account at the same time.
Open the Risk page
Go to xtriel.com/risk. Every terminal your Reporter EA has connected loads under Account risk limits.
Pick an account
Find the account you want to guard by its CustomName — the name you gave it in the EA inputs, such as Prop Firm 1 or Gold VPS.
Fill the core limits
Enter Max daily drawdown and/or Profit target for that account. Leave a field blank to disable that check — an empty field is never evaluated.
Open More limits for the rest
Expand More limits to set floating loss, minimum equity, max open positions, and the stale-terminal window. Again, blank means off.
Save changes
Click Save changes. xTriel begins evaluating the rules against every new snapshot the Reporter EA sends for that account.
Set the same rule on each account rather than one global limit. Per-account limits mean a breach on one terminal never masks or delays an alert on another.
Telegram alerts
Telegram alerts are sent by xTriel, not by the MT5 EA directly. You connect Telegram once, and the same alert engine then delivers messages for every account whose rules trip.
Create a bot with @BotFather
In Telegram, open a chat with @BotFather, send /newbot, and follow the prompts. BotFather replies with your bot token — a string like 123456789:AAExampleTelegramBotToken.
Get your chat ID
Use your personal chat ID or a group chat ID. If you want alerts in a group, add your new bot to that group first so it is allowed to post there.
Add the token and chat ID
Paste them where your setup expects them: into the EA inputs TelegramBotToken and TelegramChatId, or into Bot token and Chat ID on the dashboard Risk page.
Save changes
Click Save changes. xTriel now routes rule-breach alerts to that chat.
TelegramBotToken = 123456789:AAExampleTelegramBotToken
TelegramChatId = 123456789Send alerts to a dedicated Telegram group instead of your personal chat. You can add teammates to the group later without regenerating anything, and a bot token pasted into a group is easier to rotate than one scattered across DMs.
Test an alert
Confirm the wiring end to end before you rely on it, so you know Telegram is reachable without waiting for a real breach.
Send a test message
On the Risk page, after saving your bot token and chat ID, click Send test message. A test alert from xTriel should arrive in the target chat within a few seconds.
Trip a harmless rule
To see a real rule fire without risking anything, set a limit you know is already crossed — for example a Profit target below the account's current daily profit, or a stale-terminal window shorter than the current gap. Save, wait for the next snapshot, and confirm the alert lands.
Restore your real limits
Put the field back to the value you actually want and click Save changes again.
Confirm the bot token and chat ID are correct, and that the bot is allowed to message the target user or group. If you are testing the same breach repeatedly, wait for the alert cooldown — xTriel batches and throttles repeat alerts so a single condition does not flood the chat.
Best practices
A few habits keep risk rules useful and your Telegram signal clean rather than noisy.
- Set Max daily drawdown on every account — it is the single most valuable guardrail.
- Always add a stale-terminal window so a frozen EA or dead VPS raises an alarm instead of going silent.
- Route alerts to a dedicated group, and test with Send test message after any change to the bot token or chat ID.
- Match limits to each account's mandate — tight on a prop-firm challenge, looser on a personal account.
- Give each terminal a clear
CustomNameso an alert instantly tells you which account tripped.
- Don't treat a fired alert as an automatic stop — xTriel is read-only and never closes trades for you.
- Don't set limits so tight that normal intraday swings trip them; the constant pings train you to ignore Telegram.
- Don't paste your bot token into shared screenshots or public channels; rotate it in @BotFather if it leaks.
- Don't leave every field blank — an account with no rules is monitored on the dashboard but sends no alerts.