What is a timer interruption?
A timer interruption suspends your running timer so you can step away without losing the time already tracked. When you trigger an interruption, iTimedIT starts a 60-second grace period. If you return and resume within that window, the timer continues from exactly where it paused. If the grace period expires, the timer auto-stops and the session is saved with all time recorded up to that point.
The interruption system is handled entirely server-side using a scheduled job. This means the grace period countdown and the auto-stop both happen on the server — not in your browser. Closing the tab, losing your connection, or locking your screen does not affect the outcome. The server will stop the timer at the correct moment regardless of what the client is doing.
Triggering an interruption
To interrupt a running timer:
- Open the Timer page at app.itimedit.com.
- Click the Interrupt button while the timer is running.
- The timer pauses immediately and the 60-second grace period begins.
The timer display updates to show the interrupted state and a countdown indicating how much grace period remains.
The 60-second grace period
The grace period gives you a short window to decide whether to resume or end the session:
- Within 60 seconds: The Resume button is available. Clicking it continues the timer from the paused time.
- After 60 seconds: The server automatically stops the timer. The session is saved as a completed time entry with all time up to the interruption recorded.
The 60-second window is fixed and cannot be extended once an interruption is triggered. If you know you need more time away, consider stopping the timer manually and starting a new session when you return.
Resuming after an interruption
To resume a paused timer during the grace period:
- Return to the Timer page before the 60-second window expires.
- Click Resume.
- The timer restarts from the exact elapsed time at the moment of interruption — no time is lost and no gap is introduced in the entry.
Resuming does not create a new time entry. The session continues as a single unbroken entry, with the interruption logged as a metadata event against it.
Viewing interruption history
Every interruption is recorded as part of the time entry it affected. To review interruptions:
- Go to the Entries page.
- Open the detail view for the relevant entry.
- The interruption log shows the timestamp and duration of each pause within that session.
Interruption data is available for reporting purposes and gives managers and team members a full picture of how a tracked session unfolded.
Frequently Asked Questions
What if I do not resume within 60 seconds?
The server-side scheduler stops the timer automatically at the 60-second mark and saves the entry. You will not lose any time that was tracked before the interruption was triggered. The session appears in your Entries list as a completed entry with the interruption noted.
Are interruptions tracked in reports?
Yes. The interruption count for each entry is visible in the entry detail view on the Entries page. This lets you see at a glance how many times a session was interrupted and gives accurate context around longer or shorter entries.
Does closing the browser trigger an interruption?
No. Timers run server-side, so closing your browser, navigating away, or losing your internet connection does not pause or interrupt a running timer. The timer continues accumulating time on the server until you explicitly stop or interrupt it, or until you return and do so manually.