Record an absence using its own log type. Check the time period carefully to ensure that the entry reflects the actual absence.
- In the browser, open Working time monitoring and select Create new worktime entry.
- Select Sick leave or Vacation. To record lunch, use the Lunch log type.
- Select the user and enter the start and end times. If you are recording several days, select Same hours for multiple days and enter the date range and daily times.
- Open Preview. Check the dates, times and any errors before saving. If some days have conflicts, you can correct the details or select Create valid days only.
In the Android app, sick leave is labelled Sick Leave; in the iOS app, it is labelled Sick leave. Vacation and lunch are labelled Vacation and Lunch. Absence duration limits and checks for entries on the same day also apply to entries saved in the mobile apps.
In the browser preview, the absence times you enter are compared with the times in the worktime rule or default setting. For vacation and sick leave, the comparison primarily uses the worktime rule applicable to the user and date, if it includes the corresponding absence and the required times. Otherwise, the default times for the absence are used. The comparison times for lunch come from the default setting. Any difference from the comparison times is shown in the preview; check that the times you entered are correct.
Overlapping general worktime or absence entries may prevent saving. Check existing entries before adding a new one. Days off defined in worktime rules also affect the automatic calculation.
- Lunch, vacation and sick leave entries must have an end time. They cannot be left as running timers.
- Each of these log types can be recorded only once per user for the same start date. If an entry of the same type already exists, check and correct it instead of creating a new entry.
- When a user has a vacation entry, no other worktime entries starting on the same day can be saved for that user. This also applies to quantity-based entries.
- If a night shift that started the previous day continues into the first day of vacation, it must be followed by an uninterrupted period of time off: 24 hours for each consecutive vacation day. In this case, also check when work starts after the vacation. A running entry may prevent saving, so end it at the actual end time.
Under Default leave windows in the service settings, configure Start time, End time and Max hours separately for Lunch, Vacation and Sick leave entries. Here, Sick leave refers to the same log type as Sick leave in Working time monitoring. Max hours must be greater than 0 and no more than 24, and the duration of the default time window must not exceed this limit. If the default end time is earlier than or the same as the start time, the time window continues into the following day. Identical times mean 24 hours.
When saving an absence, its own maximum number of hours applies. The duration of other time-based entries is limited by Max consecutive hours per log entry in the service settings. A completed entry that is too long cannot be saved. First check whether the start or end date is incorrect.
A timer that has been running too long may be stopped automatically. In this case, the end time is set based on the start time and the maximum permitted duration, and the end location is shown as System. An automatic stop does not confirm that the work lasted exactly that long: check the actual working times and correct the entry if necessary before approval.
If you change the maximum duration in the settings, check the list of running entries exceeding the limit shown on the form before saving. The new limit may affect them. Automatic stopping takes place after saving, rather than immediately when the setting is saved. The timer duration limit does not apply to quantity-based entries in the same way.