PulseWatch · Guides
Updated October 2026 · written by a trader who monitors funded-style accounts daily
The daily loss limit is the rule that ends most funded accounts — not the max drawdown, not the profit target. And it fails people in a specific way: slowly, while they're not looking. A floating position drifts, the day's realized losses stack, and the firm's dashboard knows you're at 4.7% of a 5% limit — it just doesn't message you.
Every firm words it differently, but the mechanics share three parts that traders routinely get wrong:
This is the detail that quietly breaks home-made trackers, and it's worth understanding even if you never write one.
To measure a day you need to know when the broker's day began, which means knowing the
broker's timezone. The obvious way to get it is to ask the terminal: MetaTrader exposes the
server clock through TimeCurrent(), you compare it to real time, and the difference
is the offset. Simple, and correct — Monday to Friday.
The problem is that TimeCurrent() is the time of the last tick, not a
clock. When the market closes on Friday evening the ticks stop, and the value freezes
exactly where it was. It does not advance over the weekend. It sits there until the market
reopens.
So a tracker that recomputes the offset from a frozen clock concludes the broker is falling further and further behind real time — and keeps deciding that "today" is still Friday. All weekend, Friday's realized P/L is reported as today's. Come Sunday evening the number finally snaps, and anyone who checked in between saw a figure that was wrong in a way nothing on screen explained.
The fix is to only trust the clock while it's moving: compare the server time between two readings a reasonable interval apart, and accept the offset only if it advanced at roughly wall-clock speed. When it's frozen, keep using the last offset you measured while it was live — persisted, so that a restart over the weekend doesn't lose it either. The broker's days then keep rolling over correctly even while the market is shut.
If you're evaluating a third-party tool, this is a fair thing to test: check what it reports on a Saturday.
Once you know when the day started, you need the number it started at. Three candidates, and only one matches what the firm's engine does:
| Anchor | What it misses |
|---|---|
| Opening balance | Ignores positions you were already holding. Carry an underwater trade through the rollover and your loss appears to start from nothing. |
| Closed-trade total only | Ignores floating P/L entirely — you can breach an equity-based limit without closing anything, and this never sees it coming. |
| Opening equity | Nothing. This is the one that matches an equity-based daily limit, because it includes whatever you were carrying when the day began. |
So the measurement is: drop % = (day-start equity − current equity) ÷ day-start equity ×
100, with the day-start equity taken at the first reading at or after the broker day
rolled over.
An honest caveat about that last part: if your terminal was switched off when the day rolled over, the first reading of the day is whenever it came back. The anchor is then later than the firm's, and in a losing session your measured drawdown will read better than theirs. Anyone monitoring a funded account should leave the terminal running across the rollover — which is the usual argument for a VPS, and a second reason to have an offline alert.
Money moving in or out of the account is not a trading result, and a daily loss limit doesn't count it. But because it moves balance and equity, any tracker measuring raw equity change gets both of these wrong — one false alarm, one dangerous silence.
A withdrawal that isn't a loss.
Day-start equity 10,000. You withdraw 500. You place no trades.
Equity now reads 9,500. Raw calculation: (10,000 − 9,500) ÷ 10,000 = 5%
→ alert fires, on an account that hasn't traded.
Correct: add the withdrawal back. 9,500 − (−500) = 10,000 → 0%,
no alert.
A deposit that hides one.
Day-start equity 10,000. You deposit 1,000. You then lose
500 trading.
Equity now reads 10,500 — higher than you started. Raw calculation: no drawdown
at all, silence.
Correct: subtract the deposit. 10,500 − 1,000 = 9,500 → 5%,
alert fires. The deposit topped up the balance; it did not undo the loss, and the firm's
engine won't pretend it did.
The second case is the one to care about. A false alarm is annoying; a tracker that goes quiet because you happened to fund the account the same morning you were losing is actively dangerous.
A drawdown alert is not a live readout, and it shouldn't behave like one. Once you're past your threshold you stay past it — often for hours — and a system that re-sends every few seconds while that's true has converted your single most important notification into something you mute.
One message per account per day is the right contract: it fires the moment you cross, and then stays quiet. If you want to watch the number recover, that's what the dashboard is for. The alert exists to interrupt you exactly once, at the moment interruption is useful.
PulseWatch was built around exactly this. A read-only EA streams equity to a live dashboard; you set a daily drawdown percentage per your firm's rules, and Telegram pings you the moment the broker-day's equity drop crosses it — cashflows excluded, day measured in server time (including across weekends, when the broker clock stops), once per day, plus offline/recovery alerts. It also records your worst float per day, so you can see how close you actually came. First account free.
Closed-trade history shows a tidy −$120 day. It doesn't show that you were −$1,400 floating at 2pm before the position recovered. On a funded account that invisible excursion is what nearly breached the limit. Tracking the day's minimum floating P/L (sampled continuously, not reconstructed from closed trades) tells you how much risk you're really running — most traders find it uncomfortably educational.
The distinction matters because it can't be recovered after the fact. Your terminal's history tab stores what each trade closed at, not the path it took to get there, so a day's worst excursion is unrecoverable unless something was sampling equity while it happened. Two traders can post the same month of closed results with completely different risk profiles, and only the floating-P/L record tells them apart.
A practical use: compare your worst float against your firm's limit rather than your closing numbers. If your worst day closed at −1.8% but touched −4.4% floating against a 5% limit, you weren't running a 1.8% strategy. You got away with one.
Start from the hard limit you trade under and work backwards:
A threshold you'll actually respect beats a precise one you'll start ignoring. If you find yourself dismissing the alert regularly, it's too tight — widen it rather than train yourself to swipe it away.
An alert is an early-warning system, not a guarantee. Delivery depends on your terminal, the monitoring server, and Telegram all being up — and the firm's own calculation is always the authoritative one. Never use a third-party tool's figure to dispute a breach; use it to make sure you never get near one.
Two specific gaps worth knowing about. Firms differ in whether the daily limit is anchored to equity or balance at the reset, and a few use a trailing anchor that moves with your high-water mark — read your own rulebook rather than assuming the common case. And any monitor measures from its first reading of the day, so a terminal that was off at the rollover gives you an anchor the firm doesn't share.
Does this work with any prop firm? If the firm gives you an MT4/MT5 login, a monitoring EA works — it's a normal account from the terminal's point of view. Firms differ in how the daily reset is defined (balance vs equity anchor, reset time), so set your threshold conservatively.
Can monitoring get me in trouble with the firm? A read-only EA places no trades and connects to nothing but your own dashboard. It's the same category of tool as a trade journal. Rules vary, so skim your firm's EA policy — "no trading EAs" almost never means "no monitoring".
When does the day reset? On the broker's server clock, usually GMT+2/+3, so typically 5pm New York. Not your local midnight.
Why does my tracker show the wrong day over a weekend? Because MetaTrader's server time freezes at the last tick. A tracker deriving the broker timezone from that frozen value keeps thinking it's Friday until the market reopens.
Do deposits and withdrawals count? Not towards the limit — but they do move equity, so a tracker measuring raw equity change will count them. A withdrawal reads as a loss; worse, a deposit can mask a real one.
Should the alert repeat while I'm below the limit? No. Once per account per day. Anything more and you'll mute it.
What about multiple challenges at once? That's the main reason multi-account dashboards exist — every challenge on one page, one set of alerts. See the multi-account guide.
More guides: Monitor multiple MT4/MT5 accounts · Telegram alerts for MetaTrader · How to tell if your EA stopped trading · Run multiple MT5 accounts at once