Timer limits and rounding
The auto-stop cap for long-running timers, and how rounding works.
Timers that run too long
If you forget to stop a timer, Springtrack caps it rather than letting it run indefinitely. By default, a timer that's been running for 16 hours (configurable by your admin in Settings) is automatically stopped. It's clamped to the 16-hour mark — not to "right now" — so a timer left running overnight records a sensible duration, not 30 hours. The entry is flagged so you know it was auto-stopped, and you're notified.
This safety net runs for every plan; it's a data-integrity guard, not a premium feature.
Rounding
Your organisation has a rounding preference (e.g. round to the nearest 15 minutes) that applies consistently on screen and in exports. The underlying tracked seconds are always saved accurately — rounding only affects how a duration is displayed and billed, and it's never applied twice inconsistently between the timesheet and an invoice.
Very short sessions
A session of just a few seconds is still saved — Springtrack never silently drops tracked time. It's rounded per your preference like any other entry (so it may show as your minimum increment), rather than being deleted with no feedback.