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.
If someone forgets to clock out, Fuxam can automatically end the running session after a configurable duration. A background job evaluates open logs every few minutes and applies each user’s work-time model rules. Stopped sessions are labeled 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 any assigned model are not auto-stopped, which makes model assignment in User Management a prerequisite for automatic closure to act.
How it fits
| Related setting | Relationship |
|---|---|
| Enable time tracking | The auto-stop job skips institutions where time tracking is switched off. |
| Work time models on user Time Tracking tab | Each user inherits the threshold from the model active on the current date. |
| Unexcused absence threshold in General settings | Separate from auto-stop; drives unexcused-absence notifications, not session closure. |
| Manage time entries | Where Auto-stopped sessions are reviewed and corrected. |
| Work-time models and expected hours | Where models—and therefore auto-stop thresholds—are defined and assigned. |
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 | Maximum length a session may run before the background job closes it, configured per work-time model. |
| Default 12-hour window | When the model field is left empty, Fuxam uses a 12-hour default. |
| Auto-stopped label | Shown on the log when the job closes the session programmatically. |
| Auto-stop notification | Notifies the user that 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.
Go to Settings → Time Tracking and confirm Enable time tracking is on.
Open Work time models and create a model or edit an existing one.
In the model editor, find Auto-stop after forgotten clock-out.
Enter a duration (for example, 12h) or leave the field empty to use the 12-hour default.
Save the model and assign it 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 a recurring auto-stop job (every 10 minutes in production):
- Find all running time logs that have exceeded the minimum configured auto-stop window.
- Skip institutions where time tracking is not enabled.
- Resolve each user’s auto-stop duration from their active work-time model.
- Close eligible sessions, mark them Auto-stopped, and notify the user.
Stopped sessions appear in the log table with an Auto-stopped label. Users should contact a manager to correct times if the automatic end time is wrong.
Related settings on the same page
The General settings section on Settings → Time Tracking controls a separate unexcused absence threshold time—used by a different notification job, not by auto-stop. Do not confuse that threshold with the per-model auto-stop duration.
| Setting | Purpose |
|---|---|
| Auto-stop after forgotten clock-out (per model) | Closes long-running open sessions. |
| Unexcused absence threshold (general) | Triggers unexcused-absence notifications via a different job. |
Best practices
- Assign models before users track time — Without a model, auto-stop does not run for that user.
- 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 global auto-stop | Duration is per work-time model only. |
| Confusing absence threshold with auto-stop | Unexcused absence settings do not close sessions. |
| No model on user | Open sessions never auto-stop for that user. |
| 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 job closes the session when the threshold is exceeded. The exact end time is system-generated; managers should edit it in the log table if it does not match when the user actually stopped working.
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.