Two checks run quietly in the background: one watches for timers left running, the other for weeks that run unusually hot. Both only ever tell you — they never edit your time.
A timer records nothing until it stops. The entry is written at that moment, using however long the clock ran — so a timer started on Friday afternoon and noticed on Monday becomes a 70-hour entry in one click.
Time Trakkr watches for this:
Each of those is sent once per timer. A timer running for a week does not produce a week of email.
Stopping it would mean inventing an end time nobody chose, and writing that as a real entry. You know when you actually stopped working; the app does not. The nudge exists so you can stop it yourself and correct the duration while the answer is still fresh — before anything is recorded.
Under Team → your name → Notifications, clear Long-running timers. The admin escalation is separate from your own preference: it is not your notification, and its whole purpose is that the first nudge did not land.
The watchdog above only ever nudges — it never touches your timer. But when you press Stop, that is different: you are choosing an end time, not having one chosen for you, and Time Trakkr checks whether the number it is about to write makes sense.
If a timer has run for more than 16 hours, Stop refuses to record that figure. You will see a message saying nothing was saved, next to a field for the actual number of hours you worked. Enter that and press it again to log the entry with your number and stop the timer.
Nothing is guessed or rounded down on your behalf — the whole reason for the refusal is that the computed number is almost certainly wrong (most likely a timer left running by mistake), and a truncated guess would only replace one wrong number with a different one that merely looks plausible. An honest sixteen-hour day is never affected; only the hour after it is.
This check runs live, the instant you press Stop, regardless of whether the watchdog above has emailed you about this timer yet — it does not wait for the hourly sweep the watchdog runs on.
Alongside your weekly summary, Time Trakkr compares what you logged last week against your contracted weekly hours. If it reaches 120% or more (by default), you get an email naming both numbers.
What this comparison does and does not account for. It uses your contracted week as recorded on your profile. It does not subtract public holidays or approved leave — so a week containing either will read high, because you logged close to a normal week's hours in fewer days. That is often worth knowing, but it is not the same as overwork, and the email says so.
If your contracted hours are wrong, an admin can correct them under Team → your name.
Clear Busy weeks in your notification preferences to stop these.
Under Settings → Time policy → Timer watchdog:
| Setting | Default | Effect |
|---|---|---|
| Enabled | On | Turns both checks off entirely for the workspace |
| Warn after | 10 hours | When the person is nudged about a running timer |
| Escalate after | 24 hours | When admins are told as well |
| Busy week threshold | 120% | Percent of contracted hours that counts as hot |
The assistant can see running timers with the running_timers tool — for example "is anyone still running a timer?" or "any timers running more than 8 hours?". Managers and admins see the whole workspace; everyone else sees only their own.
It will not stop a timer on someone else's behalf, for the same reason the watchdog does not. It can stop your own — through the timer tool, by saying something like "stop my timer" — and if that timer has run over 16 hours, the assistant hits the same refusal the Stop button would: it will ask you for the actual hours you worked before it logs anything.
Updated 2026-08-05. Still stuck? Contact support or return to the Help Center.