Absence registration
Registers a daily entry for each ongoing open-ended period of time off so that yesterday’s day is recorded against the right activity.
How it works
When an employee starts open-ended time off (for example, ongoing sickness with no fixed return date), it stays “active” until the employee returns. This job runs daily and registers an entry for yesterday on the activity linked to the time off:
- Finds active periods — employees with at least one open-ended period of time off in progress
- Registers yesterday — for each active period that started before yesterday, a registration is created for yesterday’s date
- Safe to repeat — each registration is identified by employee, activity and date, so running the job again on the same day changes nothing
Registering yesterday (rather than today) gives the employee a window to come back to work and interrupt the time off before the day is registered. The first day is registered by the request itself, and when the time off is ended, the whole period is registered once more as a final safety net.
When it runs
The job runs automatically and only triggers on workspaces that have at least one active open-ended period of time off.
Parameters
This job has no parameters.
Job results
| Metric | Description |
|---|---|
entries_registered | Number of yesterday’s days that were newly registered |
errors | Number of failures during registration |
Troubleshooting
| Issue | Solution |
|---|---|
| Days missing on open-ended time off | Run the job manually with the run date set to the day after the missing one — catch-up runs never register a day twice |
| Active period without an activity | Nothing is registered for the period. Verify the time off policy behind that time off has an activity configured |