Auto-stop settings
Configure per work-time model auto-stop duration and understand how forgotten clock-out sessions are closed and how users are notified.
Auto-stop closes a time-tracking session that someone forgot to clock out of; you set the duration per work-time model under Settings → Management → Time Tracking. A background job checks running sessions every 10 minutes, ends the ones that ran past their limit, and labels them Auto-stopped in the log table so managers can review and correct the end time.
Auto-stop is a safety net, not a substitute for disciplined clock-out. It prevents a single open session from accumulating unrealistic hours overnight while giving institutions a predictable upper bound tied to each employment pattern.
Why it matters
Forgotten clock-outs are common in university settings—back-to-back teaching blocks, research labs without fixed end times, student desks covered by rotating shifts. Without auto-stop, one missed Pause tracking click can inflate monthly totals, trigger false overtime signals, and complicate exports sent to payroll.
Per-model configuration lets HR distinguish full-time staff (who might tolerate a longer open-session window) from part-time student workers (who need tighter closure). Users without an active work-time model are still auto-stopped, using the 12-hour default. Assign a model in User Management when you want a different limit for someone.
Key concepts
| Term | Meaning |
|---|---|
| Forgotten clock-out | A session still running (no end time yet) after the user should have paused tracking. |
| Auto-stop duration | How long a session may run without any new activity before the job closes it. Set per work-time model, between 1 and 24 hours. |
| Default 12-hour window | Used when the model field is left empty, and for users who have no active work-time model. |
| Latest activity | The clock-in or the most recent pause start or end. The auto-stop duration counts from this point. |
| Auto-stopped label | Shown in the log table's end-time column when the job closed the session. |
| Auto-stop notification | Tells the user their session was closed automatically. |
How to configure auto-stop on a work-time model
Auto-stop duration is set per work-time model, not as a single global toggle. You need permission to edit the time-tracking settings.
Go to Settings → Management → Time Tracking and make sure Enable Time Tracking is on.
In Work Time Models, click Create for a new model, or click an existing model to edit it.
In the Preferences section, find Auto-stop after forgotten clock-out.
Enter a duration between 1 and 24 hours (for example, 12h), or leave the field empty to use the 12-hour default.
Click Create Model or Update Model, then assign the model to users on their Time Tracking tab under Work time models.
Choosing a duration
Consider the longest realistic continuous work block for that model—plus a reasonable buffer—not the full legal maximum workday. Shorter thresholds surface mistakes sooner; longer thresholds reduce false closures for roles with irregular schedules. Document your institution's choice so managers know when to expect Auto-stopped labels.
| Employment pattern | Guidance (not a product default) |
|---|---|
| Student assistants with short shifts | Prefer a tighter window so overnight open sessions are rare. |
| Full-time admin with fixed office hours | A moderate window near a full day often suffices. |
| Research or lab roles with irregular ends | Longer windows reduce false closures; pair with weekly manager review. |
How automatic closure works
Fuxam runs the auto-stop job every 10 minutes:
- Skip institutions where time tracking is not enabled.
- Find running sessions and work out each user's auto-stop duration from their active work-time model (or the 12-hour default).
- Measure the time since the session's latest activity: the clock-in, or the most recent pause start or end.
- If that time is longer than the duration, close the session. The end time is set to the latest activity plus the duration, not to the moment the job ran. An open pause is closed at the same time.
- Mark the session Auto-stopped and send the user the notification Time tracking automatically stopped, which says how many hours passed and asks them to contact their manager to correct the times.
Example: someone clocks in at 08:00, takes no pause, and their model uses 10 hours. The session is closed with an end time of 18:00, even if the job only picks it up a few minutes later.
How to stop sessions at the scheduled end with a timestamp
Some institutions use timestamps (for example, a "left the site" timestamp) to show that a person is gone for the day. A timestamp template can end the session at the planned end of the workday instead of waiting for the auto-stop duration.
Go to Settings → Management → Time Tracking and open Timestamp Templates.
Create or edit a template and turn on Overwrite autostop.
Save the template.
When a user adds that timestamp and it is the last activity in their session, the job stops the session once the scheduled end time from their work-time model has passed. If the timestamp is added after the scheduled end, the session ends at the time of the timestamp. If the user has no work-time model, the session stops right away. The session is marked Auto-stopped, and the user's time-tracking managers get the notification Session stopped via timestamp (setting Time Tracking Overwrite Autostop).
Related settings on the same page
The General Settings section on Settings → Management → Time Tracking has an Unexcused Threshold time. A different notification job uses it to flag unexcused absences; it does not close sessions. Do not confuse it with the per-model auto-stop duration.
| Setting | Purpose |
|---|---|
| Auto-stop after forgotten clock-out (per model) | Closes sessions that ran too long without activity. |
| Overwrite autostop (timestamp template) | Ends the session at the scheduled end time once that timestamp is added. |
| Unexcused Threshold (General Settings) | Triggers unexcused-absence notifications through a different job. |
Best practices
- Assign models where 12 hours is the wrong limit — Without a model, everyone falls back to 12 hours.
- Train users on the notification — When they receive an auto-stop notice, they should verify the end time the same day.
- Managers review auto-stopped rows weekly — Correct end times in manage time entries before monthly export.
- Keep duration aligned with policy — Document why each model uses its chosen window so auditors understand system behavior.
Common pitfalls
| Pitfall | Result |
|---|---|
| Expecting a global auto-stop setting | Duration is per work-time model; users without a model get 12 hours. |
| Entering less than 1 hour or more than 24 hours | The model cannot be saved; the allowed range is 1–24 hours. |
| Confusing Unexcused Threshold with auto-stop | Unexcused absence settings do not close sessions. |
| Expecting the limit to count from clock-in | Starting or ending a pause counts as activity, so the duration counts again from there. |
| Ignoring Auto-stopped label | Payroll exports may include incorrect end times until corrected. |
FAQ
Can users disable auto-stop for themselves?
No. Auto-stop is governed by the institution's work-time model and background job, not by a per-user preference.
What end time does the job set?
The latest activity (clock-in or last pause start or end) plus the auto-stop duration. It is still system-generated, so managers should edit it in the log table if it does not match when the user actually stopped working.
Are users without a work-time model auto-stopped?
Yes. They use the 12-hour default.
Does auto-stop replace manual clock-out?
No. Users should still use Pause tracking in the sidebar timer. Auto-stop is a fallback for forgotten clock-outs.